CVE-2022-1359
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 affected On-Premise cnMaestro is vulnerable to an arbitrary file-write through improper limitation of a pathname to a restricted directory inside a specific route. If an attacker supplied path traversal charters (../) as part of a filename, the server will save the file where the attacker chooses. This could allow an attacker to write any data to any file in the server.
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 confidenceOn-Premise cnMaestro contains a path traversal vulnerability in a specific file upload route. The application fails to sanitize or validate filenames containing directory traversal sequences (../), allowing an authenticated or unauthenticated attacker to write arbitrary files to any location on the server filesystem accessible by the web server process.
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= 2.4.2= 3.0.0= 3.0.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 cnMaestro On-Premise is deployedCheck your infrastructure documentation or enumerate running services to confirm cnMaestro is hosted on-premise rather than using cnMaestro Cloud. On-Premise deployments run on your own servers/VMs.Affected if cnMaestro is deployed On-Premise - only On-Premise versions are affected by this vulnerability.
-
Determine installed cnMaestro versionLog into the cnMaestro web interface and navigate to the About or System Information page to view the software version. Alternatively, check the installation directory or package manager for the installed version number.Affected if The installed version matches 2.4.2, 3.0.0, or 3.0.3 exactly.
-
Verify file upload functionality is accessibleLocate the file upload routes in the cnMaestro web interface, typically found in device provisioning, firmware upload, or configuration import features. Attempt to access or identify these endpoints.Affected if The file upload functionality is exposed and accessible to users (authenticated or unauthenticated).
-
Inspect for unauthorized written files outside expected directoriesReview the cnMaestro installation directory and adjacent filesystem locations for unexpected files or directories, particularly in system folders like /etc, /var, or web root directories that were not created by normal operations.Affected if Arbitrary files exist outside the expected cnMaestro upload directories, indicating potential exploitation.
-
Check server logs for path traversal patternsExamine cnMaestro and web server (Apache/Nginx) access and error logs for requests containing '../' sequences in filename parameters, particularly on POST requests to upload endpoints.Affected if Logs show requests with '../' directory traversal sequences in filename or upload parameters.
A user is affected if they run cnMaestro On-Premise version 2.4.2, 3.0.0, or 3.0.3 with the file upload functionality exposed and accessible.
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 available. As a temporary mitigation, implement strict input validation to reject path traversal characters in filenames and restrict file write operations to a validated whitelist of allowed directories.
- Consultation4.0 h
- Implementation8.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1359 — 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-1359 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