CVE-2022-1357
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 allows an unauthenticated attacker to access the cnMaestro server and execute arbitrary code in the privileges of the web server. This lack of validation could allow an attacker to append arbitrary data to the logger command.
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 confidenceCVE-2022-1357 is a command injection vulnerability in Cambium Networks' cnMaestro On-Premise that allows unauthenticated attackers to execute arbitrary code by appending malicious data to logger commands due to lack of input validation. The vulnerability is pre-authentication, meaning no credentials are required to exploit it, and code execution occurs with web server 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 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if cnMaestro On-Premise is deployedLocate the cnMaestro web application server in your environment. This is typically accessible via HTTP/HTTPS on a configured port. Check your network inventory or scan for the cnMaestro web interface.Affected if cnMaestro On-Premise software is installed and running in your environment
-
Determine the installed cnMaestro versionLog into the cnMaestro web interface as an administrator and navigate to the About or System Information page. Alternatively, check the installation documentation or software release notes for the version number.Affected if The installed version is 2.4.2, 3.0.0, or 3.0.3 exactly
-
Verify the logger endpoint is reachableAttempt to access the logger functionality endpoint. This is typically found under system administration or diagnostics settings in the cnMaestro web interface, or by inspecting HTTP requests to the web server for logger-related paths.Affected if The logger endpoint is accessible without authentication (pre-authentication vulnerability)
-
Confirm web server is exposed to networkVerify that the cnMaestro web server is reachable from network segments accessible to untrusted users. Check firewall rules and network ACLs allowing inbound access to the cnMaestro ports.Affected if The cnMaestro web interface is exposed to untrusted networks without proper access controls
Your environment is affected if cnMaestro On-Premise version 2.4.2, 3.0.0, or 3.0.3 is installed and the web server is network-accessible, since the vulnerability allows pre-authentication command injection via logger commands.
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-supplied security patch immediately. If no patch is available, restrict network access to the cnMaestro server and implement compensating controls such as WAF rules to detect logger command injection attempts.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1357 — 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-1357 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