CVE-2019-19216: BMC Control-M/Agent 7.0.00.000 has an Insecure File Copy.

This month

HIGH 8.8DOWNGRADE

CVE-2019-19216 is a high-severity flaw (CVSS 8.8) affecting control-m\/agent. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BMC Control-M/Agent 7.0.00.000 has an Insecure File Copy.

Why this priority

High severity

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

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.1% (top 36%)
CISA exploited list	No
Weakness	CWE-269
Published	2020-04-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: bmcsoftware

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

Am I affected?

Timeline

2020-04-30 14:15 UTCPublished CVE record published
2026-06-17 02:26 UTCUpdated Record last modified

bmcsoftware control-m\/agent DOWNGRADE

Affected: 7.0.00.000

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.0.00.000

1. Check installed version

apt-cache policy control-magent || rpm -q control-magent || control-magent --version

2. No fixed release: DOWNGRADE to a release before 7.0.00.000 (Debian / Ubuntu)

apt-cache madison control-magent sudo apt install control-magent=<VERSION_BEFORE_7.0.00.000> sudo apt-mark hold control-magent

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list control-magent sudo dnf downgrade control-magent-<VERSION_BEFORE_7.0.00.000> sudo dnf versionlock add control-magent

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

control-m\/agent: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-19216 being exploited?

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

CVE-2019-19216 affects control-m\/agent. Severity is high (CVSS 8.8). BMC Control-M/Agent 7.0.00.000 has an Insecure File Copy.

How urgent is CVE-2019-19216?

Priority 47/100. High severity

Related CVEs

CVE-2025-55117 MEDIUM 5.3 UPGRADE A stack-based buffer overflow can be remotely triggered when formatting an error message in the Control-M/Agen
CVE-2025-55116 HIGH 8.8 UPGRADE A buffer overflow in the Control-M/Agent can lead to a local privilege escalation when an attacker has access
CVE-2025-55115 HIGH 8.8 UPGRADE A path traversal in the Control-M/Agent can lead to a local privilege escalation when an attacker has access t
CVE-2025-55113 CRITICAL 9.0 UPGRADE If the Access Control List is enforced by the Control-M/Agent and the C router is in use (default in Out-of-su
CVE-2025-55112 HIGH 7.4 UPGRADE Out-of-support Control-M/Agent versions 9.0.18 to 9.0.20 (and potentially earlier unsupported versions) that a

References

← Back to latest CVEs