Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: William Katsak <wkatsak@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Possibly Serious Compromise
Date: Sat, 3 Jan 2015 16:39:21 -0800	[thread overview]
Message-ID: <CAA93jw57SN+-amyJc0jDq_-+axQJtqE=Jtif+7UiU15rBmU4BQ@mail.gmail.com> (raw)
In-Reply-To: <54A88765.5040809@gmail.com>

Hmm. Port 81 is generally blocked from the outside world, which is
where lua runs. Port 80 is open, but serves up nearly no files by
default, and shouldn't be able to get to lua.

Please install tcpdump-mini. put in a usb stick and mount it. do a
tcpdump -i ge00 -w /whereverthestickis. Put the capture file up
somewhere I can get at it. Or just capture for 60 seconds to /tmp
(assuming little other traffic).You can also cut the size of the
capture down with -s 128, but that wouldn't reveal what was going on
as well.

I was, incidentally, under the impression we'd left reverse dns
lookups off in lighttpd.


On Sat, Jan 3, 2015 at 4:20 PM, William Katsak <wkatsak@gmail.com> wrote:
> I"m having a possible very serious issue with Cero. I started noticing slow
> internet access today and checked the router. I noticed a boatload of dns
> resolutions. These push the router load over 1, and eventually dnsmasq
> crashes and has to be restarted.
>
> After tracing it for an hour or so and ruling out misbehaving software on
> the local net, I enabled logging in dnsmasq and saw that the resolutions
> were coming from 127.0.0.1. I kept running netstat -up until I saw some of
> the connections, and saw that they were coming from lua. All of the requests
> seem to be reverse DNS lookups of all kinds of crazy IPs.
>
> These requests look like part of some attack/compromise. If I kill
> lighthttpd, everything settles down and runs fine. If I turn it back on, the
> traffic starts again. I am thinking some kind of vulnerability in the http
> server allowing malformed requests from outside? I can't for the life of me
> figure out how they are getting in though. I have very few changes to the
> firewall config, and only a few port forwards.
>
> I'll send more info as I get it.
>
> Anyone else see anything like this?
>
> -Bill
>
>
> --
> ****************************************
> William Katsak <wkatsak@gmail.com>
> ****************************************
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

      reply	other threads:[~2015-01-04  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04  0:20 William Katsak
2015-01-04  0:39 ` Dave Taht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw57SN+-amyJc0jDq_-+axQJtqE=Jtif+7UiU15rBmU4BQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=wkatsak@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox