CVE-2018-0545: LXR version 1.0.0 to 2.3.0 allows remote attackers to execute arbitrary OS commands via unspecified vectors.

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2018-0545 is a critical-severity flaw (CVSS 9.8) affecting lxr. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

LXR version 1.0.0 to 2.3.0 allows remote attackers to execute arbitrary OS commands via unspecified vectors.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.9% (top 13%)
CISA exploited list	No
Weakness	CWE-78
Published	2018-04-09
Last modified	2026-06-17

Publisher (CNA): JPCERT/CC · Vendor: lxr project

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

Am I affected?

Timeline

2018-04-09 13:29 UTCPublished CVE record published
2026-06-17 01:31 UTCUpdated Record last modified

lxr project lxr UPGRADE

Affected: >= 1.0.0 and <= 2.3.0

Fixed in: newer than 2.3.0

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy lxr || rpm -q lxr || lxr --version

2. UPGRADE to newer than 2.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade lxr

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade lxr

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison lxr sudo apt install lxr=<VERSION_BEFORE_1.0.0> sudo apt-mark hold lxr

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list lxr sudo dnf downgrade lxr-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add lxr

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.

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-2018-0545?

lxr: upgrade to newer than 2.3.0. Exact commands for each OS are on this page.

Is CVE-2018-0545 being exploited?

CVE-2018-0545 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-2018-0545 affect?

CVE-2018-0545 affects lxr. Severity is critical (CVSS 9.8). LXR version 1.0.0 to 2.3.0 allows remote attackers to execute arbitrary OS commands via unspecified vectors.

How urgent is CVE-2018-0545?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs