CVE-2022-48074
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 · uneditedAn issue in NoMachine before v8.2.3 allows attackers to execute arbitrary commands via a crafted .nxs file.
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 confidenceNoMachine before v8.2.3 contains a command injection vulnerability where a specially crafted .nxs configuration file can be used to execute arbitrary commands on the target system. The vulnerability stems from insufficient validation of content within .nxs files, allowing an attacker to embed malicious command sequences that are executed when the file is processed by the NoMachine client or server.
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< 8.2.3CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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 NoMachine versionLocate the NoMachine installation and retrieve its version number using system utilities or the application's --version flagAffected if The installed version is less than 8.2.3
-
Verify NoMachine client is presentConfirm NoMachine client software is installed on the systemAffected if NoMachine client exists and version is below 8.2.3
-
Confirm .nxs file processing capabilityCheck if NoMachine is configured to handle .nxs configuration files, which is the default behavior for the clientAffected if The NoMachine client can process .nxs files (default enabled state)
-
Audit recently opened .nxs filesReview system logs, recent files, or NoMachine session history for any .nxs files that have been opened, particularly from untrusted sourcesAffected if Any .nxs file from an untrusted source has been opened with a vulnerable NoMachine version
The system is affected if NoMachine version is below 8.2.3 and the client has processed a specially crafted .nxs file, allowing potential command injection.
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 · scoped8.2.3
Upgrade NoMachine to version 8.2.3 or later. Until patched, avoid opening .nxs files from untrusted sources and consider implementing application whitelisting to block execution of unauthorized processes.
8.2.3
- Backup your current NoMachine installation and configuration data
- Download NoMachine version 8.2.3 or later from the official NoMachine website (kb.nomachine.com)
- Uninstall the current (vulnerable) version of NoMachine
- Install the newly downloaded version 8.2.3 or later
- Verify the installation was successful by checking the NoMachine version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-48074 — 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-2022-48074 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