Suse Lifecycle Management Server vulnerabilitiesRanked by how likely they are to be used.
Suse Lifecycle Management Server is made by Novell. We track 5 published vulnerabilities in it, across 5 versions. None of them is on the list of flaws known to be exploited today. If you run Suse Lifecycle Management Server, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Suse Lifecycle Management Server vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Suse Lifecycle Management Server's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Suse Lifecycle Management Server 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.3%CVE-2013-3710Medium
SUSE Lifecycle Management Server (SLMS) before 1.3.7 does not generate a new secret key when the service starts, which allows remote attackers to defeat intended cryptographic protection mechanisms by leveraging...
- 0.9%CVE-2010-1325Medium
Cross-site request forgery (CSRF) vulnerability in the apache2-slms package in SUSE Lifecycle Management Server (SLMS) 1.0 on SUSE Linux Enterprise (SLE) 11 allows remote attackers to hijack the authentication of...
- 0.5%CVE-2013-3709High
WebYaST 1.3 uses weak permissions for config/initializers/secret_token.rb, which allows local users to gain privileges by reading the Rails secret token from this file.
- 0.4%
SUSE Lifecycle Management Server before 1.1 uses world readable postgres credentials, which allows local users to obtain sensitive information via unspecified vectors.
- 0.3%CVE-2013-7042Medium
SUSE Lifecycle Management Server (SLMS) before 1.3.7 uses world-readable permissions for the secret keys, which allows local users to gain privileges via unspecified vectors.
Running Suse Lifecycle Management Server? 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
SUSE Lifecycle Management Server (SLMS) before 1.3.7 does not generate a new secret key when the service starts, which allows remote attackers to defeat intended cryptographic protection mechanisms by leveraging knowledge of this key from a product installation elsewhere.
- Matched to
- Suse Lifecycle Management Server 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 Suse Lifecycle Management Server, across 5 versions.
None of Suse Lifecycle Management Server's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Suse Lifecycle Management Server. 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.