Opensuse vulnerabilitiesRanked by how likely they are to be used.
Opensuse is made by Suse. We track 5 published vulnerabilities listed under that exact name, across 3 versions. None of them is on the list of flaws known to be exploited today. Suse lists newer releases under their own names, such as Opensuse Factory, so check those pages too.
We keep watching the known-exploited list.
Is Opensuse listed under other names? Yes.
Suse also lists Opensuse under more specific names, such as Opensuse Factory and Opensuse Leap. 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 Opensuse vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Opensuse's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Opensuse 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.
- 2.4%CVE-2011-0469Critical
Code injection in openSUSE when running some source services used in the open build service 2.1 before March 11 2011.
- 1.8%CVE-2010-0230High
SUSE Linux Enterprise 10 SP3 (SLE10-SP3) and openSUSE 11.2 configures postfix to listen on all network interfaces, which might allow remote attackers to bypass intended access restrictions.
- 1.1%CVE-2017-3224High
Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber.
- 0.3%CVE-2007-2654Medium
xfs_fsr in xfsdump creates a .fsr temporary directory with insecure permissions, which allows local users to read or overwrite arbitrary files on xfs filesystems.
- 0.3%
sudo in SUSE openSUSE 10.3 does not clear the stdin buffer when password entry times out, which might allow local users to obtain a password by reading stdin from the parent process after a sudo child process exits.
Running Opensuse? 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
Code injection in openSUSE when running some source services used in the open build service 2.1 before March 11 2011.
- Matched to
- Opensuse 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 5 published vulnerabilities listed under the name Opensuse, across 3 versions.
None of Opensuse's vulnerabilities is on the list of flaws known to be exploited today.
Suse also lists Opensuse under more specific names, such as Opensuse Factory and Opensuse Leap. 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 Opensuse. 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.