CVE-2022-40713
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. Multiple Relative Path Traversal issues exist in different specific endpoints via the file parameter, allowing a remote authenticated attacker to read files on the filesystem arbitrarily.
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 confidenceNOKIA 1350OMS R14.2 contains multiple path traversal vulnerabilities in specific endpoints via the file parameter. An authenticated remote attacker can supply relative path sequences (e.g., ../../../etc/passwd) to read arbitrary files from the filesystem, potentially exposing sensitive system files or configuration data.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 is installedLocate the Nokia 1350 Optical Management System installation directory or service on the target host. Check system services, installed applications, or documentation that references this product.Affected if The product is not present on the system.
-
Verify the installed version is 14.2Check the installed version of Nokia 1350 OMS against the version information. Compare your installed version to the affected range (version 14.2).Affected if The installed version is exactly 14.2.
-
Identify web interface or API endpointsLocate the web management interface or API endpoints for the Nokia 1350 OMS. These are typically accessible via HTTP/HTTPS on configured ports.Affected if The web interface or API endpoints are not accessible.
-
Confirm authentication is enabledVerify that authentication is required and properly configured for accessing the management interface. Check if default credentials or valid user accounts exist.Affected if Authentication is not required (anonymous access allowed).
-
Identify endpoints accepting file parameterEnumerate the application endpoints that accept a file parameter in request handling. These are the specific endpoints where path traversal may be possible.Affected if No endpoints accepting a file parameter are found.
The environment is affected only if Nokia 1350 Optical Management System version 14.2 is installed AND the web interface with vulnerable file parameter endpoints is accessible with valid authentication.
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 dataImplement strict input validation and path sanitization on all file parameter endpoints. Use allowlists for permitted paths, normalize file paths, and reject requests containing traversal sequences (..). Consider applying the principle of least privilege to limit file access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40713 — 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-40713 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