dbcve.org
Command InjectionWeakness · CWE-77

CVE-2022-35503

HIGH · 7.5 CVSS v3.1 Published 2024-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper verification of a user input in Open Source MANO v7-v12 allows an authenticated attacker to execute arbitrary code within the LCM module container via a Virtual Network Function (VNF) descriptor. An attacker may be able execute code to change the normal execution of the OSM components, retrieve confidential information, or gain access other parts of a Telco Operator infrastructure other than OSM itself.

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 confidence

Improper verification of user input in Open Source MANO v7-v12 allows authenticated attackers to inject and execute arbitrary code within the LCM (Lifecycle Management) module via specially crafted VNF (Virtual Network Function) descriptors. This input validation failure in descriptor processing enables code execution with the privileges of the LCM container.

MitigationImplement strict input validation and sanitization on all VNF descriptor fields in the LCM module before processing. Treat all descriptor data as untrusted and apply whitelist validation, length limits, and sanitization of any field used in code execution contexts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OSM installation and version
    Check if Open Source MANO is installed by looking for OSM package files, directories, or running processes. Common locations include /opt/osm, /usr/osm, or check for osm* processes. Run 'osm --version' or check installed packages with package manager.
    Affected if The installed OSM version is between v7 and v12 inclusive
  2. Verify LCM module is active
    Check if the LCM (Lifecycle Management) module is running. This can be done by listing running processes related to LCM (e.g., osm-lcm, lifecycle-management) or checking service status if OSM runs as a service.
    Affected if The LCM module is active and processing VNF descriptors
  3. Confirm VNF descriptor processing is enabled
    Inspect the OSM configuration to verify that VNF descriptor parsing/processing is enabled. Check configuration files in /etc/osm/ or the directory where OSM config is stored for settings related to vnfd, descriptor, or lcm processing.
    Affected if VNF descriptor processing is enabled in the OSM configuration
  4. Check authentication controls on descriptor upload
    Review access controls on the OSM LCM API endpoints that accept VNF descriptors. Determine if unauthenticated or low-privilege users can submit descriptors.
    Affected if Authenticated users or any users can submit VNF descriptors to the LCM module

You are affected if OSM versions v7-v12 are installed and the LCM module is actively processing VNF descriptors from authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on all VNF descriptor fields in the LCM module before processing. Treat all descriptor data as untrusted and apply whitelist validation, length limits, and sanitization of any field used in code execution contexts.

Recommended fix Moderate confidence

OSM version 13 or later (latest stable release)

  1. 1. Identify the currently deployed OSM version by checking the installed packages or the OSM dashboard version information
  2. 2. Back up all OSM configurations, databases, and VNF descriptors before performing any upgrade
  3. 3. Upgrade the OSM installation to the latest stable release (version 13 or later, which contains the fix for this vulnerability)
  4. 4. After upgrading, verify that the LCM module container is running the updated version
  5. 5. Test that VNF descriptor parsing works correctly with the upgraded version
  6. 6. Validate that the command injection vulnerability is no longer present by ensuring proper input sanitization in VNF descriptors
Caveat Review OSM release notes for any breaking changes between v7-v12 and the target version; may require updates to existing VNF descriptors or workflows

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35503 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35503 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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