CVE-2017-2233
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 Installer of PDF Digital Signature Plugin (G2.30) and earlier, distributed till June 29, 2017 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 confidenceThe PDF Digital Signature Plugin installer (G2.30 and earlier, distributed through June 29, 2017) contains an untrusted search path vulnerability allowing DLL hijacking. An attacker can place a malicious DLL in an unspecified directory that the installer searches when running, causing it to be loaded with elevated privileges and enabling privilege escalation.
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<= g2.30CVSS 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.0/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 installed PDF Digital Signature Plugin versionCheck the version of the Moj Pdf Digital Signature plugin installed on the system. Common locations include the installation directory or program files. Look for version information in file properties or the plugin's about/info dialog.Affected if The installed version is G2.30 or earlier (any version number less than or equal to G2.30)
-
Locate the installer executableFind the installer file used to install the PDF Digital Signature Plugin. Search for installer files in download folders, temp directories, or any directory where the file was originally placed before installation.Affected if The installer file is present on the system and was stored or run from an untrusted or writable directory such as a shared network folder, downloads folder, or desktop
-
Inspect directories the installer may searchExamine the directories that the installer searches when running, particularly the current working directory where the installer was executed. Look for any unexpected DLL files present in those locations.Affected if Unexpected or unknown DLL files exist in the directory from which the installer was run or in directories the installer searches during execution
-
Check for DLL files with suspicious characteristicsReview any DLL files found in installer search paths for unusual names, recent modification dates, or DLLs that do not belong to the legitimate PDF Digital Signature Plugin installation.Affected if Foreign or malicious DLL files are present in directories that the installer queries during its execution sequence
-
Verify installation source locationDetermine from which directory the installer was originally executed. Check the installer logs, system logs, or user documentation to confirm the source location.Affected if The installer was run from a directory that is writable by other users or is shared/untrusted (e.g., public downloads, network share)
A user is affected if the PDF Digital Signature Plugin version is G2.30 or earlier AND the installer was executed from or has access to directories containing untrusted or malicious DLL files.
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 dataUpdate to PDF Digital Signature Plugin G2.31 or later. Ensure the installer is run from a trusted directory and verify no untrusted DLLs exist in directories the installer searches.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2233 — 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-2017-2233 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