Re: Scans on port 17107

From: Myself (nobody_at_noplace.com)
Date: 11/26/05

  • Next message: bodhi: "Re: iptables rule causes delay in password prompt"
    Date: Fri, 25 Nov 2005 19:32:22 -0600
    
    

    On Fri, 25 Nov 2005 17:44:49 -0600, Moe Trin wrote:

    > On Fri, 25 Nov 2005, in the Usenet newsgroup comp.os.linux.security, in
    > article <dm8541$mcl$1@bn2.blue.net>, Myself wrote:
    >
    >>Yesterday, over a course of about 3 minutes, my firewall logged 1366
    >>hits on port 17107. This occurred immediately after connecting, and from
    >>1255 different sources. Some were TCP and others UDP.
    >
    > Hard to say - seeing both TCP and UDP to the same port number (other than
    > occasionally on 53 for DNS) is unusual.

    That seemed a bit odd to me.

    > 17107 is a 'user-land' port,
    > meaning it's not a regular server. The "standard" answer for your
    > observation is that the person who had that IP number before you was
    > running a server of some kind - I'd suspect a game server of some kind,
    > but that's purely a guess.

    This is what I suspect. As I said in my original post, I often get a
    series of hits on some single port (and not any certain one), and I have
    always come to the conclusion that it is from the previous port. However,
    the number of these did get my attention. I use fwlogwatch and it send me
    an email report. When I opened mutt and saw the report with over 1000
    lines, I did notice :)

    > I really don't think I'd worry about it. You have nothing
    running on
    > that port, so there is nothing to exploit.

    Right. I have no open incoming ports to my knowledge. I've had them
    checked on several of the security sites.

    >>I tried to do a Google search on port 17107 but couldn't find anything,
    >>and I don't have anything in /etc/services or another listing of ports
    >>that I have.
    >
    > As above. Try http://www.iana.org/assignments/port-numbers to get the
    > official list,

    I have a second list besides /etc/services, and I believe it is from
    there.. It dates back to 2002 (could update), but I check with it in
    addition to /etc/services.

    > but remember there is no force of law behind that. If someone wants to
    > run a mail server on 17107, they could. Most people wouldn't know it
    > exists there, because you look for "well known services" on "well known
    > ports" in this case 25. Also, no windoze virus writer has ever
    > registered his worm/trojan/what-ever with IANA.

    True. But often it can give you a clue to what it might be.

    Did two of my original posts show up on the list? For some reason, I got
    two, showing a difference of 2 seconds, I believe...


  • Next message: bodhi: "Re: iptables rule causes delay in password prompt"

    Relevant Pages

    • RE: Logs: Many hits with source port of 80
      ... I have seen similar hits for the past three months. ... Are you sure yours are TCP? ... Subject: Logs: Many hits with source port of 80 ... where the source port is set to tcp 80 and the destination port is some ...
      (Incidents)
    • Re: Port 25 blocking ????
      ... But I should see some hits on my permit statements in my ACL if it was ... If they are port 25 blocking, that would prevent my telnet attempt, ... Timing out is a typical reaction for a firewalled connection. ...
      (comp.dcom.sys.cisco)
    • Re: New program/virus is making the rounds?
      ... >Most hits were port 27374, now almost all are port 1433. ... >What new program hit the web now??? ... which filters the crap out of the emails BEFORE it infects ...
      (comp.security.firewalls)
    • Re: New program/virus is making the rounds?
      ... >Most hits were port 27374, now almost all are port 1433. ... >What new program hit the web now??? ... which filters the crap out of the emails BEFORE it infects ...
      (comp.security.firewalls)
    • McAfee Personal Firewall
      ... I just purchased the McAfee Personal Firewall this weekend ... the hits that have probably always been there. ... that was using a "Microsoft-DS" service or program. ... If you want to allow traffic on this port, ...
      (microsoft.public.security)