CVE-2018-5204: ML Report version Between 2.00.000.0000 and 2.18.628.5980 contains a vulnerability that could allow remote att

This week

CRITICAL 9.8REMOTEUPGRADE

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

ML Report version Between 2.00.000.0000 and 2.18.628.5980 contains a vulnerability that could allow remote attacker to download and execute remote arbitrary file by setting the arguments to the activex method. this can be leveraged for code execution.

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.3% (top 16%)
CISA exploited list	No
Weakness	CWE-434
Published	2018-12-28
Last modified	2026-06-17

Publisher (CNA): KrCERT/CC · Vendor: infraware-global

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

Am I affected?

Timeline

2018-12-28 16:29 UTCPublished CVE record published
2026-06-17 01:59 UTCUpdated Record last modified

infraware-global ml report UPGRADE

Affected: >= 2.00.000.0000 and <= 2.18.628.5980

Fixed in: newer than 2.18.628.5980

Safe to downgrade to: a release before 2.00.000.0000

1. Check installed version

apt-cache policy ml-report || rpm -q ml-report || ml-report --version

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

sudo apt update && sudo apt install --only-upgrade ml-report

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ml-report

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 2.00.000.0000 (Debian / Ubuntu)

apt-cache madison ml-report sudo apt install ml-report=<VERSION_BEFORE_2.00.000.0000> sudo apt-mark hold ml-report

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

dnf --showduplicates list ml-report sudo dnf downgrade ml-report-<VERSION_BEFORE_2.00.000.0000> sudo dnf versionlock add ml-report

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-5204?

ml report: upgrade to newer than 2.18.628.5980. Exact commands for each OS are on this page.

Is CVE-2018-5204 being exploited?

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

CVE-2018-5204 affects ml report. Severity is critical (CVSS 9.8). ML Report version Between 2.00.000.0000 and 2.18.628.5980 contains a vulnerability that could allow remote attacker to download and execute remote arbitrary file by setting the arguments to the activex method. this can be leveraged for code

How urgent is CVE-2018-5204?

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

References

← Back to latest CVEs