CVE-2019-6019
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 · uneditedUntrusted search path vulnerability in STAMP Workbench installer all versions allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
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 confidenceThis is a DLL hijacking (untrusted search path) vulnerability in the STAMP Workbench installer. The installer loads dynamic-link libraries from directories that are not secure, allowing an attacker to place a malicious DLL in a location where it will be loaded by the installer with elevated 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 dataall versionsCVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Identify if Ipa Stamp Workbench installer is presentSearch common download directories (Downloads, Desktop, temp folders) for installer files named 'stamp workbench', 'ipa stamp', or similar. Also check Program Files for the installed application.Affected if The installer executable or installation files are found in a directory writable by non-admin users (e.g., Downloads, temp, network shares)
-
Check the security of the directory containing the installerRight-click the folder containing the installer, go to Properties > Security, and verify that only trusted users have Write or Modify permissions. Check for 'Everyone', 'Users', or 'Authenticated Users' with Write access.Affected if The directory is writable by unprivileged users or the public (such as a shared network folder or user-downloads directory)
-
Review recent installer execution historyCheck Windows Event Viewer > Application logs for recent entries from 'STAMP Workbench' or 'Ipa Stamp' installer. Also review browser download history or installation logs.Affected if The installer was recently run from an untrusted location (Downloads folder, shared drive, or temp directory)
-
Verify the installer is from an official sourceCheck the installer file properties: right-click > Properties > Digital Signatures. Verify the signature is from 'IPA' or the official vendor and the certificate is valid.Affected if The installer is unsigned, has an invalid signature, or was obtained from an unofficial source
You are affected if the Ipa Stamp Workbench installer exists in or was previously run from a directory that unprivileged users can write to, enabling DLL hijacking with elevated privileges.
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 the vendor patch when released. In the interim, run the installer from a trusted, secure directory and ensure the working directory cannot be controlled by unprivileged users.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6019 — 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-6019 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