CVE-2023-30759
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 · uneditedThe driver installation package created by Printer Driver Packager NX v1.0.02 to v1.1.25 fails to detect its modification and may spawn an unexpected process with the administrative privilege. If a non-administrative user modifies the driver installation package and runs it on the target PC, an arbitrary program may be executed with the administrative privilege.
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 · high confidencePrinter Driver Packager NX versions 1.0.02 through 1.1.25 fail to verify the integrity of their driver installation packages, allowing a non-privileged user to modify the package and trigger execution of arbitrary code with administrative privileges. This is a local privilege escalation vulnerability stemming from missing integrity checks on the installer.
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>= 1.0.02, < 1.1.26CVSS 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.
-
Locate Printer Driver Packager NX installationSearch for 'Printer Driver Packager NX' in Windows Add/Remove Programs, or check common installation directories such as C:\Program Files\Ricoh or C:\Program Files (x86)\Ricoh for the executable PDnxWizard.exe or similarAffected if The software is found installed on the system
-
Identify installed versionRight-click the main executable (typically named something like PDnxWizard.exe or PrinterDriverPackagerNX.exe) in the installation folder, select Properties, and view the File Version or Product Version field on the Details tabAffected if The version displayed is 1.0.02, 1.0.03, 1.0.04, 1.1.x, or any version from 1.0.02 up to and including 1.1.25
-
Compare version to vulnerable rangeReview the identified version against the affected range: versions 1.0.02 through 1.1.25 are vulnerable; version 1.1.26 and later are notAffected if The installed version is greater than or equal to 1.0.02 AND less than 1.1.26
-
Check for existing driver packagesLook for any previously generated driver package files (typically .cab or similar installer package files) in the output directory where Printer Driver Packager NX saves created driver packagesAffected if Any driver packages were created using the vulnerable version of the software
If Printer Driver Packager NX is installed with a version between 1.0.02 and 1.1.25 (inclusive), the system is affected by this vulnerability.
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.
dbcve · scoped1.1.26
Update Printer Driver Packager NX to version 1.1.26 or later, which includes proper integrity verification for driver packages. Regenerate all existing driver packages using the updated version.
1.1.26
- Navigate to the official Ricoh support website and locate the Printer Driver Packager Nx download page
- Download Printer Driver Packager Nx version 1.1.26 or later
- Verify the integrity of the downloaded installer using checksums if provided
- Close any running instances of Printer Driver Packager Nx
- Uninstall the current version of Printer Driver Packager Nx from the system
- Install the newly downloaded version (1.1.26 or later)
- Verify the installation was successful and the version is correct
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30759 — 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-2023-30759 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