CVE-2019-18245
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 · uneditedReliable Controls LicenseManager versions 3.4 and prior may allow an authenticated user to insert malicious code into the system root path, which may allow execution of code with elevated privileges of the application.
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 confidenceReliable Controls LicenseManager versions 3.4 and prior contains an authenticated code injection vulnerability where users can insert malicious code into the system root path, enabling execution with elevated application privileges.
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<= 3.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Reliable Controls LicenseManager is installedCheck the system for the presence of Reliable Controls LicenseManager software. Look in standard program directories or use system inventory tools to identify if this application is deployed.Affected if The software is present on the system.
-
Determine the installed version of LicenseManagerAccess the application properties or About section within LicenseManager, or check the installed programs list in the system control panel to find the exact version number.Affected if The installed version is 3.4 or any prior version (3.4, 3.3, 3.2, etc.).
-
Confirm administrative or elevated access existsReview user accounts that have administrative or elevated privileges to the LicenseManager application, as this is an authenticated vulnerability requiring valid credentials.Affected if Any user account with administrative or elevated privileges to the application exists.
-
Inspect system root directories for unexpected filesExamine the system root path (such as C:\ or installation directory root) for newly created or modified executable files, scripts, or DLLs that were not intentionally placed there.Affected if Suspicious or unknown executable files, scripts, or DLLs are found in the system root path.
-
Review application logs for code execution attemptsCheck LicenseManager application logs and Windows system event logs for entries indicating execution of files from system root directories or unexpected command activity.Affected if Logs show execution of files from system root or suspicious command activity.
A user is affected if Reliable Controls LicenseManager version 3.4 or prior is installed and any authenticated user has administrative access to the application.
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 patch for CVE-2019-18245; until patched, restrict administrative access to trusted personnel only and monitor for unauthorized code execution or suspicious file activity in system directories.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18245 — 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-18245 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