CVE-2019-19218
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 has Insecure Password Storage.
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 stores passwords insecurely, likely in plaintext or with weak encryption. This allows attackers with access to the stored credentials to retrieve them in recoverable form, potentially enabling privilege escalation or unauthorized access to managed systems.
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 installed BMC Control-M/Agent versionUse system package management tools or check the Control-M Agent installation directory for version information. Common commands include: ctmversion, ctmdiag, or checking registry entries on Windows. On Unix/Linux, inspect /opt/ctm directory or use vendor-provided version commands.Affected if The installed version is exactly 7.0.00.000. Note that only this specific version is listed as affected.
-
Locate Control-M Agent configuration directoriesSearch for Control-M installation directories. Default locations may include /opt/ctm (Linux/Unix) or C:\Program Files\BMC\Control-M (Windows). Look for subdirectories containing configuration files such as agent.cfg, ctmcd.ini, or similar configuration files.Affected if Control-M Agent version 7.0.00.000 is installed and configuration directories exist on the system.
-
Inspect credential storage filesExamine configuration and credential storage files within the Control-M Agent directories. Look for files that may contain stored credentials such as parameter files, configuration databases, or credential cache files. Common file patterns may include .par, .cfg, or database files.Affected if Credential storage files exist and contain user credentials or authentication data for managed systems.
-
Verify password storage formatOpen and inspect the credential storage files identified in the previous step. Examine whether passwords appear in plaintext, encoded in simple Base64, or encrypted with weak/known algorithms. Compare the stored value against known plaintext passwords if accessible.Affected if Passwords are stored in plaintext, simple encoding (like Base64), or weak encryption that can be reversed without access to external key material.
You are affected if BMC Control-M/Agent version 7.0.00.000 is installed AND credential storage files contain passwords in plaintext, simple encoding, or weak reversible encryption.
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 dataUpgrade to a patched version of BMC Control-M/Agent and rotate all stored credentials. Implement proper password hashing with salted cryptographic hashes or secure encryption for any remaining stored credentials.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19218 — 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-19218 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