CVE-2019-11216: BMC Smart Reporting 7.3 20180418 allows authenticated XXE within the import functionality

This month

MEDIUM 6.5UPGRADE

CVE-2019-11216 is a medium-severity flaw (CVSS 6.5) affecting remedy smart reporting. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BMC Smart Reporting 7.3 20180418 allows authenticated XXE within the import functionality. One can import a malicious XML file and perform XXE attacks to download local files from the server, or do DoS attacks with XML expansion attacks. XXE with direct response and XXE OOB are allowed.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Weakness	CWE-434, CWE-611
Published	2019-12-04
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: bmc

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

Am I affected?

Timeline

2019-12-04 20:15 UTCPublished CVE record published
2026-06-17 02:12 UTCUpdated Record last modified

bmc remedy smart reporting UPGRADE

Affected: >= 9.1.03 and <= 9.1.03.001 · >= 9.1.04 and <= 9.1.04.002 · >= 18.05 and <= 18.05.05 · >= 19.02 and <= 19.02.01

Fixed in: newer than 19.02.01

Safe to downgrade to: a release before 9.1.03

1. Check installed version

apt-cache policy remedy-smart-reporting || rpm -q remedy-smart-reporting || remedy-smart-reporting --version

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

sudo apt update && sudo apt install --only-upgrade remedy-smart-reporting

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade remedy-smart-reporting

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

apt-cache madison remedy-smart-reporting sudo apt install remedy-smart-reporting=<VERSION_BEFORE_9.1.03> sudo apt-mark hold remedy-smart-reporting

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

dnf --showduplicates list remedy-smart-reporting sudo dnf downgrade remedy-smart-reporting-<VERSION_BEFORE_9.1.03> sudo dnf versionlock add remedy-smart-reporting

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-2019-11216?

remedy smart reporting: upgrade to newer than 19.02.01. Exact commands for each OS are on this page.

Is CVE-2019-11216 being exploited?

CVE-2019-11216 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-11216 affect?

CVE-2019-11216 affects remedy smart reporting. Severity is medium (CVSS 6.5). BMC Smart Reporting 7.3 20180418 allows authenticated XXE within the import functionality. One can import a malicious XML file and perform XXE attacks to download local files from the server, or do DoS attacks with XML expansion attacks. XX

How urgent is CVE-2019-11216?

Priority 47/100. Public exploit reference

Related CVEs

CVE-2019-1010147 MEDIUM 5.4 MITIGATE UPGRADE Yellowfin Smart Reporting All Versions Prior to 7.3 is affected by: Incorrect Access Control - Privileges Esca

References

← Back to latest CVEs