# Juniper Networks
**URL:** https://cog.discourse.group/t/juniper-networks/1098
**Category:** useful info
**Created:** [December 19, 2015, 1:41am UTC](https://cog.discourse.group/t/juniper-networks/1098 "2015-12-19T01:41:52Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)
#### Post date: [December 19, 2015, 1:41am UTC](https://cog.discourse.group/t/juniper-networks/1098/1 "2015-12-19T01:41:52Z")
> **[Juniper firewalls compromised by bad code: What you need to know](https://www.networkworld.com/article/3016992/juniper-firewalls-compromised-by-spy-code-what-you-need-to-know.html)**
>
> Juniper Networks is warning customers to patch their NetScreen enterprise firewalls against bad code that enables attackers to take over the machines and decrypt VPN traffic among corporate sites and with mobile employees.
If your workplace is using this, you might want to double-check everything.
I don’t take the “but nobody has used it yet” very seriously.
---
### Author:  [@CryHavok](https://cog.discourse.group/u/CryHavok)
#### Post date: [December 19, 2015, 9:16am UTC](https://cog.discourse.group/t/juniper-networks/1098/2 "2015-12-19T09:16:31Z")
Somebody put it there for a reason. There’s zero probability that it hasn’t been used by those behind it.
And, well, no surprise that nobody’s reported it being used. Few organisations have a clue about the amount of malware on their estate, even when that malware is over a decade old, is responsible for more network sessions than anything other than their DNS servers or even is responsible for more network traffic than anything else.
---
### Author:  [@ClockWorkXon](https://cog.discourse.group/u/ClockWorkXon)
#### Post date: [December 19, 2015, 10:10am UTC](https://cog.discourse.group/t/juniper-networks/1098/3 "2015-12-19T10:10:56Z")
> [@CryHavok](#):
>
> There’s zero probability that it hasn’t been used by those behind it.
That’s pretty much what I thought. Such a strong statement that “nobody has actually used it”, when it would be difficult to prove such a thing. How many installs did they check on, and how?
Despite what Microsoft claims, I seriously doubt some of these major problems “just happened”.