Floodlight vulnerabilitiesRanked by how likely they are to be used.
Floodlight is made by Atlassian. We track 4 published vulnerabilities listed under that exact name, across 6 versions. None of them is on the list of flaws known to be exploited today. Atlassian lists newer releases under their own names, such as Floodlight Controller, so check those pages too.
We keep watching the known-exploited list.
Is Floodlight listed under other names? Yes.
Atlassian also lists Floodlight under more specific names, such as Floodlight Controller. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Floodlight vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Floodlight's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Floodlight flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.9%CVE-2015-6569Medium
Race condition in the LoadBalancer module in the Atlassian Floodlight Controller before 1.2 allows remote attackers to cause a denial of service (NULL pointer dereference and thread crash) via a state manipulation...
- 1.3%CVE-2020-18683Critical
Floodlight through 1.2 has poor input validation in checkFlow in StaticFlowEntryPusherResource.java because of undefined fields mishandling.
- 1.3%CVE-2020-18684Critical
Floodlight through 1.2 has an integer overflow in checkFlow in StaticFlowEntryPusherResource.java via priority or port number.
- 1.3%CVE-2020-18685Critical
Floodlight through 1.2 has poor input validation in checkFlow in StaticFlowEntryPusherResource.java because of unchecked prerequisites related to TCP or UDP ports, or group or table IDs.
Running Floodlight? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Race condition in the LoadBalancer module in the Atlassian Floodlight Controller before 1.2 allows remote attackers to cause a denial of service (NULL pointer dereference and thread crash) via a state manipulation attack.
- Matched to
- Floodlight on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name Floodlight, across 6 versions.
None of Floodlight's vulnerabilities is on the list of flaws known to be exploited today.
Atlassian also lists Floodlight under more specific names, such as Floodlight Controller. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Floodlight. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.