CVE-2022-40712
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 was discovered in NOKIA 1350OMS R14.2. Reflected XSS exists under different /cgi-bin/R14.2* endpoints.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in NOKIA 1350OMS R14.2 optical management system. The vulnerability is present in multiple endpoints under the /cgi-bin/R14.2* path, allowing attackers to inject malicious scripts through unsanitized user input that gets reflected back in HTTP responses.
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= 14.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm Nokia 1350 OMS installationAccess the web interface of the optical management system by navigating to the device IP or hostname on the standard management port (typically 443 or 8080). Verify the product name is displayed in the login page or system information section.Affected if The Nokia 1350 Optical Management System web interface is accessible and the product is present in the environment.
-
Identify installed software versionLocate the version information within the management interface. This is typically found in the system information, about, or settings page. The version may also be visible in the HTML source or HTTP response headers.Affected if The installed version is exactly 14.2 (R14.2).
-
Locate CGI endpoints under /cgi-bin/R14.2*Review the application's URL structure or sitemap to identify CGI scripts under the /cgi-bin/R14.2 path. These may include endpoints for device configuration, status monitoring, or administrative functions.Affected if Endpoints matching the /cgi-bin/R14.2* pattern are present and accessible in the application.
-
Inspect parameter handling in affected endpointsSubmit a test request to accessible /cgi-bin/R14.2* endpoints with a benign parameter value and examine the HTTP response. Check whether the supplied value is reflected back in the response body without apparent sanitization or encoding.Affected if User-supplied parameters are reflected verbatim in the HTTP response without input validation or output encoding.
A user is affected if they are running Nokia 1350 Optical Management System version 14.2 with accessible /cgi-bin/R14.2* CGI endpoints that reflect user input without sanitization in HTTP responses.
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 vendor-provided patches for R14.2 and implement proper input validation and output encoding for all user-supplied parameters in affected /cgi-bin/R14.2* endpoints to prevent script injection.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40712 — 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-40712 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