Hi,
i havent heard about any attacks in the wild, yet.
As i wrote...you cant protect yourself against this tcp bug.
(I dont think anyone out there has a box running with all ports closed
and is using only console to manage it...).
Once you run BGP, OSPF, SSH, FTP or whatever you are vulnerable e
Hi,
.-- My secret spy satellite informs me that at 1/12/10 9:22 AM Jonas
Frey wrote:
However 7.4 seems to be not vulnerable. Atleast the version i have here
(7.4I20071211_1225_pgoyette) is not affected. Therefor i guess
everything below this (atleast) is not vulnerable...that would explain
w
Tim,
firewall filters help somewhat. But still someone can spoof this packet
and make it appear from one of your bgp peers, customers, management
network, etc etc.
There is no 100% effective way to protect against it.
E.g. if you peer with 10.0.0.22 (your upstream) and you are 10.0.0.21
and i kno
Jonas,
Correct firewall filters *will* block it as the firewall filter will keep
the tcp port even responding. However if your router has a tcp port open to
a specific subnet IP's on that subnet will be able to exploit. In other
words there is no specific firewall filter that can be put in place t
Hello,
i have tried exploiting this on various junos version (8.2, 8.5, 9.2),
all of them crashed immediatly at tcp_input() and rebooted after dumping
the core.
However 7.4 seems to be not vulnerable. Atleast the version i have here
(7.4I20071211_1225_pgoyette) is not affected. Therefor i guess
e
* Barry Greene:
> The information is in the security advisory.
Are the PSNs the security advisory you are referring to?
I didn't see a security advisory as such, and I'm wondering if I'm
missing anything.
--
Florian Weimer
BFK edv-consulting GmbH http://www.bfk.de/
Kriegs
> > The information is in the security advisory.
>
> Are the PSNs the security advisory you are referring to?
>
> I didn't see a security advisory as such, and I'm wondering if I'm
> missing anything.
Yes. Juniper has been using the Tech Bulletins (PSNs, etc.) for our Security
Advisories.
h
It was on the original bulletin and was removed today 01/07/09.
Sorry to scare everyone :)
Sent from my iPhone
On Jan 7, 2010, at 2:13 PM, "Dan Evans"
mailto:pzdev...@gmail.com>> wrote:
Tommy,
I just checked all PSN notifications associated with this SIRT bulletin and
*none* of them list 10.
Tommy,
I just checked all PSN notifications associated with this SIRT bulletin and
*none* of them list 10.x as an affected release.
On Thu, Jan 7, 2010 at 2:58 PM, Tommy Perniciaro
wrote:
> How can that be the case when 10.x was released after 1/09 and it's on
> the list of affected junos versi
How can that be the case when 10.x was released after 1/09 and it's on
the list of affected junos versions?
Sent from my iPhone
On Jan 7, 2010, at 11:24 AM, "harbor235" wrote:
> Any code released after 1/28/09 has this issue fixed ...
>
> mike
>
> On Thu, Jan 7, 2010 at 1:18 PM, Brad Fleming
Any code released after 1/28/09 has this issue fixed ...
mike
On Thu, Jan 7, 2010 at 1:18 PM, Brad Fleming wrote:
> I think it depends how the vulnerability is discovered. If its discovered
> by groups that are likely to exploit the issue, I'd prefer Juniper tell me
> NOW. If it is discovered i
> Does anyone know how far Juniper is planning to back port this fix
> into their software?
>
> I am basically asking because I am sure a few of us are running some
> older Juniper hardware and would like to figure out where we stand.
>
> Like 8.1x is not EOL until 05/06/2010 but ENG support st
I think it depends how the vulnerability is discovered. If its
discovered by groups that are likely to exploit the issue, I'd prefer
Juniper tell me NOW. If it is discovered internally by Juniper
technicians (or in a trusted customer lab), I'm OK with Juniper fixing
the issue and releasing
On Thursday 07 January 2010 09:04:11 pm Paul Stewart wrote:
> Anyone know why some issues identified as early as
> January 2009 are only being "released" now almost a year
> later? Just curious on some of these security alerts
> and timeframe...
My guess is they wanted to have a fix out befor
Hey all,
Does anyone know how far Juniper is planning to back port this fix
into their software?
I am basically asking because I am sure a few of us are running some
older Juniper hardware and would like to figure out where we stand.
Like 8.1x is not EOL until 05/06/2010 but ENG support stopp
> Anyone know why some issues identified as early as January 2009 are only
> being "released" now almost a year later? Just curious on some of these
> security alerts and timeframe...
If Juniper finds a security DDOS vulnerability, and it's not general knowledge,
I'd prefer them to integrate the
On Thu, 2010-01-07 at 08:04 -0500, Paul Stewart wrote:
> Anyone know why some issues identified as early as January 2009 are only
> being "released" now almost a year later?
someone forgot to hit the 'send' button? ;)
Interestingly enough, all of the PRs mentioned in these bulletins are
not ava
Just curious on some of these
security alerts and timeframe...
Paul
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Tore Anderson
Sent: Thursday, January 07, 2010 7:56 AM
To: Juniper-Nsp
Subject: [j-nsp] JUNOS vul
Hi list,
I think most of you will find this interesting:
http://www.theregister.co.uk/2010/01/07/juniper_critical_router_bug/
http://praetorianprefect.com/archives/2010/01/junos-juniper-flaw-exposes-core-routers-to-kernal-crash/
Best regards,
--
Tore Anderson
Redpill Linpro AS - http://www.redp
19 matches
Mail list logo
