CVE-2019-19219
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBMC Control-M/Agent 7.0.00.000 allows Arbitrary File Download.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBMC Control-M/Agent version 7.0.00.000 contains an arbitrary file download vulnerability, likely due to insufficient path validation or access controls that allow an attacker to request and download sensitive files from the host system without proper authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.0.00.000CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if BMC Control-M/Agent is installedLook for Control-M/Agent processes running on the system or check installed software listings for BMC Control-MAffected if Control-M/Agent software is present on the system
-
Determine the installed Control-M/Agent versionUse system inventory tools or check Control-M version information to confirm the exact version numberAffected if The installed version is 7.0.00.000 exactly
-
Check if Control-M/Agent service is network-accessibleIdentify open ports or services associated with Control-M/Agent and determine if they accept remote connectionsAffected if The Control-M/Agent service is exposed to the network without proper access restrictions
-
Assess authentication and authorization controlsReview access control configurations for the Control-M/Agent service to determine if unauthenticated or unauthorized file requests are possibleAffected if The service allows file download requests without sufficient path validation or authorization checks
-
Verify if sensitive files are accessible via the agent interfaceIf the agent provides a web interface or API endpoint for file operations, test whether arbitrary file system paths can be requestedAffected if The agent permits downloading files outside the expected application directory without proper validation
You are affected if BMC Control-M/Agent version 7.0.00.000 is installed and its service is accessible, allowing unauthorized file downloads due to insufficient path validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches for CVE-2019-19219; if no patch available, restrict network access to the Control-M/Agent services and audit file access controls on affected systems.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data