Main Page | Report this Page
Linux Forum Index  »  Linux Security  »  Security Breached...
Page 1 of 2    Goto page 1, 2  Next

Security Breached...

Author Message
Randy Yates...
Posted: Tue Aug 11, 2009 9:18 pm
Guest
Hi,

I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

Also, due to a wireless network adapter card that's not very
well-suported under Fedora 11, I was forced to run WEP security on my
wireless network. Yeah yeah, I know - that's no security at all.

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

If the reported address of the intruder was a typical local, private
network address like 192.168.x.y, I'd just chalk it up to a neighbor
that hacked my network. But 119.205.217.141 is a public IP address
somewhere in Asia. So I'm thinking he must have come in over the WAN
port.

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

So I feel it is highly unlikely he came in over the WAN port, but if he
came in over the wireless, I don't see how he could have a public
address in Asia.

Any theories on how my security was breached would be appreciated.
--
Randy Yates % "And all that I can do
Digital Signal Labs % is say I'm sorry,
mailto://yates at (no spam) ieee.org % that's the way it goes..."
http://www.digitalsignallabs.com % Getting To The Point', *Balance of Power*, ELO
 
Allen Kistler...
Posted: Tue Aug 11, 2009 11:23 pm
Guest
Randy Yates wrote:
Quote:
I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

[snip]

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

[snip]

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

Any theories on how my security was breached would be appreciated.

If that connection was from the stated IP address, then it didn't
"bounce" off anything else in your home network, since your laptop and
your router had to be able to route packets back to the intruder.

I'd say the VNC port isn't/wasn't so blocked as you thought.

So maybe it was a multi-stage hack. First he got admin access to your
router. Then he discovered what you had internally and set up his own
forwarding.

Getting access to your router may or may not have been a multi-step
process, as well, involving first compromising whatever you have
directly facing the Internet. If that's only ssh, then that's how he
got in. (You may choose from any of the following options: ssh.)

Alternate ports are pretty worthless against anything but the kiddiest
of scripts. Try telneting to an ssh server sometime. ssh not only
tells your telnet client that it's an ssh server, it self-identifies
what version. ssh has good security, if you set it up, but that
security is not even slightly based on evasion.

One thing I do think is certain is that, unless you set up VNC
forwarding yourself (unlikely by your account), he got into your router
somehow.

If the router is directly accessible from the Internet, maybe it was one
or two steps easier for him. Have you ever scanned yourself?

Then there's always Trojans that you downloaded unwittingly, making that
his first point of entry before hitting your router.

Also, how really sure are you that he was the first and that this was
his only time?
 
Randy Yates...
Posted: Wed Aug 12, 2009 2:23 am
Guest
Allen Kistler <ackistler at (no spam) oohay.moc> writes:

Quote:
Randy Yates wrote:
I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

[snip]

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

[snip]

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

Any theories on how my security was breached would be appreciated.

If that connection was from the stated IP address, then it didn't
"bounce" off anything else in your home network, since your laptop and
your router had to be able to route packets back to the intruder.

I'd say the VNC port isn't/wasn't so blocked as you thought.

So maybe it was a multi-stage hack. First he got admin access to your
router. Then he discovered what you had internally and set up his own
forwarding.

Getting access to your router may or may not have been a multi-step
process, as well, involving first compromising whatever you have
directly facing the Internet. If that's only ssh, then that's how he
got in. (You may choose from any of the following options: ssh.)

Alternate ports are pretty worthless against anything but the kiddiest
of scripts. Try telneting to an ssh server sometime. ssh not only
tells your telnet client that it's an ssh server, it self-identifies
what version. ssh has good security, if you set it up, but that
security is not even slightly based on evasion.

One thing I do think is certain is that, unless you set up VNC
forwarding yourself (unlikely by your account), he got into your
router somehow.

If the router is directly accessible from the Internet, maybe it was
one or two steps easier for him. Have you ever scanned yourself?

Hi Allen,

First of all Allen, thank you for your response.

I just did a "self-scan" and got the expected results. How would an intruder
get into my router? Port 80 is open but NATed to my desktop machine.

Quote:
Then there's always Trojans that you downloaded unwittingly, making
that his first point of entry before hitting your router.

Under linux? Not likely. I can't think of any raw installs I've
done (download and unzip, ./configure, make, make install) - the
rest are from repositories that are trusted.

Quote:
Also, how really sure are you that he was the first and that this was
his only time?

Not at all. But so what? The theory questions on how he's doing it
are going to be the same, no?
--
Randy Yates % "With time with what you've learned,
Digital Signal Labs % they'll kiss the ground you walk
mailto://yates at (no spam) ieee.org % upon."
http://www.digitalsignallabs.com % '21st Century Man', *Time*, ELO
 
ArameFarpado...
Posted: Wed Aug 12, 2009 3:32 am
Guest
Em Quarta 12 Agosto 2009 04:18, Randy Yates escreveu:

Quote:
Hi,

I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

Also, due to a wireless network adapter card that's not very
well-suported under Fedora 11, I was forced to run WEP security on my
wireless network. Yeah yeah, I know - that's no security at all.

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

If the reported address of the intruder was a typical local, private
network address like 192.168.x.y, I'd just chalk it up to a neighbor
that hacked my network. But 119.205.217.141 is a public IP address
somewhere in Asia. So I'm thinking he must have come in over the WAN
port.

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

So I feel it is highly unlikely he came in over the WAN port, but if he
came in over the wireless, I don't see how he could have a public
address in Asia.

Any theories on how my security was breached would be appreciated.

test your firewall with this site

https://www.grc.com/x/ne.dll?bh0bkyd2
 
ArameFarpado...
Posted: Wed Aug 12, 2009 3:38 am
Guest
Em Quarta 12 Agosto 2009 09:23, Randy Yates escreveu:

Quote:

I just did a "self-scan" and got the expected results. How would an
intruder get into my router? Port 80 is open but NATed to my desktop
machine.

and is your vnc server using port 80?
 
Bit Twister...
Posted: Wed Aug 12, 2009 8:50 am
Guest
On Wed, 12 Aug 2009 13:18:10 -0400, David W. Hodgins wrote:

Quote:
The upnp "feature" allows programs such as skype, to configure a port
on the router, that will be forwarded to the network interface it's
using, without the router's admin password being required. Turning off upnp
means you'll have to manually configure every the router, and the
programs, for every computer on your lan.

Just an fyi, skype will still work for the average user/use
with Universal plug-n-play disabled in the router.

Guessing your skype/upnp example would be needed if your node is to be
a skype Supernode.
 
David W. Hodgins...
Posted: Wed Aug 12, 2009 9:38 am
Guest
On Wed, 12 Aug 2009 04:23:42 -0400, Randy Yates <yates at (no spam) ieee.org> wrote:


Quote:
I just did a "self-scan" and got the expected results. How would an intruder
get into my router? Port 80 is open but NATed to my desktop machine.
Under linux? Not likely. I can't think of any raw installs I've

See http://www.gnucitizen.org/blog/hacking-the-interwebs/

In your router, change it's ip address (you'll have to restart networking
after updating the address in the config file), admin username and password.
Also, turn off upnp. Doesn't matter what os your using.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
 
Randy Yates...
Posted: Wed Aug 12, 2009 10:27 am
Guest
"David W. Hodgins" <dwhodgins at (no spam) nomail.afraid.org> writes:

Quote:
On Wed, 12 Aug 2009 04:23:42 -0400, Randy Yates <yates at (no spam) ieee.org> wrote:


I just did a "self-scan" and got the expected results. How would an intruder
get into my router? Port 80 is open but NATed to my desktop machine.
Under linux? Not likely. I can't think of any raw installs I've

See http://www.gnucitizen.org/blog/hacking-the-interwebs/

In your router, change it's ip address (you'll have to restart networking
after updating the address in the config file), admin username and password.
Also, turn off upnp. Doesn't matter what os your using.

Regards, Dave Hodgins

Thanks Dave for the information, Dave.

I've turned off UPNP (never knew what it was for anyway) and changed
passwords. By "change it's ip address" do you mean the address seen on
the WAN side? No, I'm not willing to do that YET as I have a domain
pointed to it. If you can convince me why it's critical enough to go to
the trouble of updating the domain name, I'll do it.
--
Randy Yates % "Though you ride on the wheels of tomorrow,
Digital Signal Labs % you still wander the fields of your
mailto://yates at (no spam) ieee.org % sorrow."
http://www.digitalsignallabs.com % '21st Century Man', *Time*, ELO
 
Randy Yates...
Posted: Wed Aug 12, 2009 10:28 am
Guest
ArameFarpado <a-farpado.spam at (no spam) netcabo.pt> writes:

Quote:
Em Quarta 12 Agosto 2009 04:18, Randy Yates escreveu:

Hi,

I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

Also, due to a wireless network adapter card that's not very
well-suported under Fedora 11, I was forced to run WEP security on my
wireless network. Yeah yeah, I know - that's no security at all.

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

If the reported address of the intruder was a typical local, private
network address like 192.168.x.y, I'd just chalk it up to a neighbor
that hacked my network. But 119.205.217.141 is a public IP address
somewhere in Asia. So I'm thinking he must have come in over the WAN
port.

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

So I feel it is highly unlikely he came in over the WAN port, but if he
came in over the wireless, I don't see how he could have a public
address in Asia.

Any theories on how my security was breached would be appreciated.

test your firewall with this site

https://www.grc.com/x/ne.dll?bh0bkyd2

Thanks ArameFarpado. Done, and it seems I "passed".
--
Randy Yates % "Though you ride on the wheels of tomorrow,
Digital Signal Labs % you still wander the fields of your
mailto://yates at (no spam) ieee.org % sorrow."
http://www.digitalsignallabs.com % '21st Century Man', *Time*, ELO
 
ArameFarpado...
Posted: Wed Aug 12, 2009 10:34 am
Guest
Em Quarta 12 Agosto 2009 17:28, Randy Yates escreveu:

Quote:
ArameFarpado <a-farpado.spam at (no spam) netcabo.pt> writes:

Em Quarta 12 Agosto 2009 04:18, Randy Yates escreveu:

Hi,

I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

Also, due to a wireless network adapter card that's not very
well-suported under Fedora 11, I was forced to run WEP security on my
wireless network. Yeah yeah, I know - that's no security at all.

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

If the reported address of the intruder was a typical local, private
network address like 192.168.x.y, I'd just chalk it up to a neighbor
that hacked my network. But 119.205.217.141 is a public IP address
somewhere in Asia. So I'm thinking he must have come in over the WAN
port.

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

So I feel it is highly unlikely he came in over the WAN port, but if he
came in over the wireless, I don't see how he could have a public
address in Asia.

Any theories on how my security was breached would be appreciated.

test your firewall with this site

https://www.grc.com/x/ne.dll?bh0bkyd2

Thanks ArameFarpado. Done, and it seems I "passed".

did you test the port that vnc is using?
 
Randy Yates...
Posted: Wed Aug 12, 2009 10:40 am
Guest
ArameFarpado <a-farpado.spam at (no spam) netcabo.pt> writes:

Quote:
Em Quarta 12 Agosto 2009 17:28, Randy Yates escreveu:

ArameFarpado <a-farpado.spam at (no spam) netcabo.pt> writes:

Em Quarta 12 Agosto 2009 04:18, Randy Yates escreveu:

Hi,

I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

Also, due to a wireless network adapter card that's not very
well-suported under Fedora 11, I was forced to run WEP security on my
wireless network. Yeah yeah, I know - that's no security at all.

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

If the reported address of the intruder was a typical local, private
network address like 192.168.x.y, I'd just chalk it up to a neighbor
that hacked my network. But 119.205.217.141 is a public IP address
somewhere in Asia. So I'm thinking he must have come in over the WAN
port.

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

So I feel it is highly unlikely he came in over the WAN port, but if he
came in over the wireless, I don't see how he could have a public
address in Asia.

Any theories on how my security was breached would be appreciated.

test your firewall with this site

https://www.grc.com/x/ne.dll?bh0bkyd2

Thanks ArameFarpado. Done, and it seems I "passed".

did you test the port that vnc is using?

I tested all ports from 0 to 1023. The only ones open are the ones
I want to be open, namely, http (80) and svn (3690).
--
Randy Yates % "Though you ride on the wheels of tomorrow,
Digital Signal Labs % you still wander the fields of your
mailto://yates at (no spam) ieee.org % sorrow."
http://www.digitalsignallabs.com % '21st Century Man', *Time*, ELO
 
Bit Twister...
Posted: Wed Aug 12, 2009 10:42 am
Guest
On Wed, 12 Aug 2009 15:55:58 -0400, David W. Hodgins wrote:
Quote:
On Wed, 12 Aug 2009 14:50:52 -0400, Bit Twister <BitTwister at (no spam) mouse-potato.com> wrote:

Just an fyi, skype will still work for the average user/use
with Universal plug-n-play disabled in the router.

True. That was just one example of a program that can use upnp.

I understand, I just wanted the lurkers not to panic or enable upnp if
they use skype. :(

Quote:
The scariest part of the attack scenario, is that everything is
working as designed. There is no software bug involved (except
in those routers where the attack can force it to be reset to
the factory defaults). It's a protocol design problem that
affects most routers.

Yes and I think we can look forward to other attacks on the router
from the LAN. I run privoxy proxy server with a rule to block access
to my router just to reduce the threat from the browser path.
 
David W. Hodgins...
Posted: Wed Aug 12, 2009 11:18 am
Guest
On Wed, 12 Aug 2009 12:27:33 -0400, Randy Yates <yates at (no spam) ieee.org> wrote:

Quote:
passwords. By "change it's ip address" do you mean the address seen on
the WAN side? No, I'm not willing to do that YET as I have a domain

No. I mean the address of the router, as seen from the lan. Typically
a router will have an address of 192.168.10.1. Change it to something
like 192.168.10.87, or any other value it can use, that is non-standard.

After you make that change, you'll have to change the line
GATEWAY=192.168.10.1
to match the new value, and then restart the interface.

That change will have to be made on all clients on your lan.

The upnp "feature" allows programs such as skype, to configure a port
on the router, that will be forwarded to the network interface it's
using, without the admins password being required. Turning off upnp
means you'll have to manually configure every the router, and the
programs, for every computer on your lan.

The attack uses xml to send a soap request to the router, from your
computer. Changing the gateway address makes it much harder for the
attacker to find your router.

If the attacker succeeds, they can alter the dns servers used by
your router, and any computer on your lan that gets the dns addresses
from the router, via dhcp. That means they can intercept all traffic.

Another aspect of the attack, is that some routers can be reset to
factory defaults, forcing the admin username, and password back to
the defaults, and turning on upnp.

By changing the gateway address, you ensure that networking will simply
fail, rather then having the attack succeed, if the router gets reset.

It's also a good idea to manually enter the dns server addresses in
your computers, instead of relying on the addresses from the router.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
 
Allen Kistler...
Posted: Wed Aug 12, 2009 12:00 pm
Guest
Randy Yates wrote:
Quote:
Allen Kistler writes:

[snip]


I just did a "self-scan" and got the expected results. How would an intruder
get into my router? Port 80 is open but NATed to my desktop machine.

I don't know for sure how, but here's the reasoning again.

1. A foreign IP address was hitting your laptop.
2. It had to be hitting your laptop directly, since the connection was
TCP and the laptop and other network devices needed to complete the
return connection.
3. The only way for a foreign IP address to hit an internal device
directly is if the router was configured to forward it.
4. You didn't configure the router to forward VNC to your laptop, so
somebody else did, presumably the intruder.

There's also the possibility that he unconfigured when you discovered
him. As for the path, if he didn't compromise the router directly, then
he compromised something on the inside and bounced back to the router
from there. If you've got logs you can trust, you've got some forensics
to do.

In your previous post you said you had ssh open, but you didn't think it
was ssh that he used. Well, this guy's not performing magic. Whatever
you had open, he used that. If ssh was truly the only thing open, then
that's what he used.

Quote:
Then there's always Trojans that you downloaded unwittingly, making
that his first point of entry before hitting your router.

Under linux? Not likely. I can't think of any raw installs I've
done (download and unzip, ./configure, make, make install) - the
rest are from repositories that are trusted.

Firefox plugins. How much do you install them? How much do you trust
them? The correct answers should be "little" and "not at all."

Plus your laptop is mobile. Presumably you go places with it.

Again, you say every compromise vector is unlikely, but you also say it
happened. You even watched part of it in real time. So "unlikely"
doesn't matter any more. If he didn't get in using something you had
open previously, then he found another vector inside to open up
something on his own.

Quote:
Also, how really sure are you that he was the first and that this was
his only time?

Not at all. But so what? The theory questions on how he's doing it
are going to be the same, no?

Why? If he did it once or a thousand times, how will knowing his method
(if determined in any way, exactly or otherwise) enlighten you to how
many times he did it? How will knowing his method enlighten you to how
many others (if any) have done it?
 
Unruh...
Posted: Wed Aug 12, 2009 12:15 pm
Guest
Randy Yates <yates at (no spam) ieee.org> writes:

Quote:
ArameFarpado <a-farpado.spam at (no spam) netcabo.pt> writes:

Em Quarta 12 Agosto 2009 17:28, Randy Yates escreveu:

ArameFarpado <a-farpado.spam at (no spam) netcabo.pt> writes:

Em Quarta 12 Agosto 2009 04:18, Randy Yates escreveu:

Hi,

I have a typical home network that looks like this:

machine type connection type
------------ --------------
desktop pc 1 wired
desktop pc 2 wireless
laptop wireless
network printer wired

dlink dir 655 router
Time-warner "surfboard" cable modem

I run Fedora 11, fully updated, on all computers.

I have the vnc port blocked at the router so I presumed it was safe to
leave my vnc passwords open on machines on my local network.

Also, due to a wireless network adapter card that's not very
well-suported under Fedora 11, I was forced to run WEP security on my
wireless network. Yeah yeah, I know - that's no security at all.

Well, some stranger vnc'ed into my laptop. I was there when it happened
and the vnc server i'm using (fedora 11) displays the connection's ip
address and it was 119.205.217.141.

If the reported address of the intruder was a typical local, private
network address like 192.168.x.y, I'd just chalk it up to a neighbor
that hacked my network. But 119.205.217.141 is a public IP address
somewhere in Asia. So I'm thinking he must have come in over the WAN
port.

But if he came in over the WAN port (e.g., over ssh), he would have had
to make a hop via my desktop pc since that's where ssh is NATed to.
Further, the desktop PC's ssh port was non-standard, root access is
disabled, and the main account password is quite long and secure.

So I feel it is highly unlikely he came in over the WAN port, but if he
came in over the wireless, I don't see how he could have a public
address in Asia.

Any theories on how my security was breached would be appreciated.

test your firewall with this site

https://www.grc.com/x/ne.dll?bh0bkyd2

Thanks ArameFarpado. Done, and it seems I "passed".

did you test the port that vnc is using?

I tested all ports from 0 to 1023. The only ones open are the ones
I want to be open, namely, http (80) and svn (3690).

You do know that 3690 is not a port "from 0 to 1023"?
 
 
Page 1 of 2    Goto page 1, 2  Next
All times are GMT - 5 Hours
The time now is Tue Dec 01, 2009 12:30 am