CVE-2022-40715
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. An Absolute Path Traversal vulnerability exists for a specific endpoint via the logfile 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 · moderate confidenceNokia 1350 OMS R14.2 contains an Absolute Path Traversal vulnerability in a specific endpoint through the logfile parameter. A remote authenticated attacker can supply absolute file paths to read arbitrary files on the filesystem, potentially exposing sensitive system configuration files, credentials, or user 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 installed product and versionAccess the Nokia 1350 OMS administrative interface or check system inventory for the installed software version. Verify the exact version number is 14.2.Affected if The installed version is Nokia 1350 OMS version 14.2 exactly.
-
Locate endpoints accepting logfile parameterReview the web application's available endpoints or API routes. Identify any endpoint that accepts a logfile parameter in the request (typically GET or POST).Affected if An endpoint exists that accepts a logfile parameter for log retrieval.
-
Verify endpoint accessibilityAttempt to access the identified endpoint from a network perspective. Determine if the endpoint is exposed externally or accessible without VPN from untrusted networks.Affected if The vulnerable endpoint is network-accessible from untrusted sources.
-
Review authentication configurationCheck the authentication mechanism for the endpoint. Determine if it properly validates user credentials or if there are misconfigurations that could allow bypass.Affected if Authentication is missing, misconfigured, or can be bypassed for the logfile parameter endpoint.
A system is affected if it is running Nokia 1350 OMS version 14.2 and exposes an endpoint accepting a logfile parameter that can be accessed with valid credentials or through an authentication bypass.
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 the logfile parameter, restricting access to only intended log directories. Use basename() or equivalent to strip directory components and validate against an allowlist of permitted paths.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40715 — 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-40715 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