Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-13313: libosinfo 1.5.0 allows local users to discover credentials by listing a process, because credentials are passe

42
This month
HIGH 7.8WATCHLISTDOWNGRADEMITIGATEMITIGATE

CVE-2019-13313 is a high-severity flaw (CVSS 7.8) affecting libosinfo, fedora, enterprise linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

libosinfo 1.5.0 allows local users to discover credentials by listing a process, because credentials are passed to osinfo-install-script via the command line.

Why this priority

  • High severity
  • On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 63%)
CISA exploited listNo
WeaknessCWE-200
Published2019-07-05
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: fedoraproject · libosinfo · redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

libosinfo libosinfo DOWNGRADE
Affected: 1.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.5.0
1. Check installed version
apt-cache policy libosinfo || rpm -q libosinfo || libosinfo --version
2. No fixed release: DOWNGRADE to a release before 1.5.0 (Debian / Ubuntu)
apt-cache madison libosinfo sudo apt install libosinfo=<VERSION_BEFORE_1.5.0> sudo apt-mark hold libosinfo
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list libosinfo sudo dnf downgrade libosinfo-<VERSION_BEFORE_1.5.0> sudo dnf versionlock add libosinfo
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fedoraproject fedora MITIGATE
Affected: 29 · 30
Fixed in: no fixed release known
Safe to downgrade to: a release before 29
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux MITIGATE
Affected: 8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux eus MITIGATE
Affected: 8.1 · 8.2 · 8.4 · 8.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server aus MITIGATE
Affected: 8.2 · 8.4 · 8.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.2
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
redhat enterprise linux server tus MITIGATE
Affected: 8.2 · 8.4 · 8.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.2
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-13313?

libosinfo: downgrade or apply the listed mitigation; fedora: mitigate or apply the listed mitigation; enterprise linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-13313 being exploited?

CVE-2019-13313 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-13313 affect?

CVE-2019-13313 affects libosinfo, fedora, enterprise linux. Severity is high (CVSS 7.8). libosinfo 1.5.0 allows local users to discover credentials by listing a process, because credentials are passed to osinfo-install-script via the command line.

How urgent is CVE-2019-13313?

Priority 42/100. High severity; On your watchlist

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.