dbcve.org
Enterprise Nfv Infrastructure SoftwareApplication · Cisco

CVE-2022-20929

HIGH · 7.8 CVSS v3.1 Published 2023-03-10
Fix available
A fix is available. Upgrade to 4.9.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
A vulnerability in the upgrade signature verification of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an unauthenticated, local attacker to provide an unauthentic upgrade file for upload. This vulnerability is due to insufficient cryptographic signature verification of upgrade files. An attacker could exploit this vulnerability by providing an administrator with an unauthentic upgrade file. A successful exploit could allow the attacker to fully compromise the Cisco NFVIS system.

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 confidence

The vulnerability exists in Cisco NFV Infrastructure Software's upgrade signature verification mechanism. An unauthenticated local attacker can bypass cryptographic signature checks on upgrade files, allowing them to provide a malicious firmware/image file to an administrator for upload. Successful exploitation grants the attacker full control of the NFVIS system.

MitigationApply the vendor patch from Cisco when available. Until then, implement strict controls on upgrade file handling: verify file来源, use out-of-band integrity verification, and limit who can initiate upgrades.

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
Enterprise Nfv Infrastructure SoftwareApplication
Affected:>= 3.5.1, < 4.9.1

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 NFVIS version
    Run 'show version' command in the NFVIS CLI or check the version file at /opt/infra/var/infra_version to determine the installed Cisco NFV Infrastructure Software version
    Affected if Version is >= 3.5.1 and < 4.9.1
  2. Verify upgrade feature is enabled
    Check if the Software Management or upgrade functionality is configured and accessible. Use 'show running-config | include upgrade' or access the administration web UI to confirm upgrade capability is available
    Affected if Upgrade functionality is enabled and accessible in the system
  3. Inspect upgrade file staging area
    Examine the default upgrade staging directory (typically /opt/infra/packages or /var/upgrade) for any unexpected or unauthorized .bin, .img, or .iso files present on the system
    Affected if Unexpected image files exist in upgrade directories that were not explicitly uploaded by trusted administrators
  4. Review upgrade-related logs
    Check system logs in /var/log/ for entries related to upgrade operations, signature validation events, or file imports. Look for gaps or anomalies in the log sequence
    Affected if Missing, altered, or suspicious entries exist in upgrade or file validation logs
  5. Audit upgrade access controls
    Review user accounts and role-based access controls (RBAC) to determine which users have privileges to initiate upgrades or upload firmware images
    Affected if Unrestricted or unauthorized user accounts have upgrade or image upload permissions

The environment is affected if the installed NFVIS version falls within 3.5.1 through 4.9.1 and the upgrade feature is accessible to potential attackers

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
Upgrade available Upgrade to 4.9.1 or later
Fixed in 4.9.1
Interim mitigation

Apply the vendor patch from Cisco when available. Until then, implement strict controls on upgrade file handling: verify file来源, use out-of-band integrity verification, and limit who can initiate upgrades.

Recommended fix High confidence

Cisco NFVIS version 4.9.1 or later (4.x stable release)

  1. 1. Identify the current version of Cisco Enterprise NFV Infrastructure Software running on the system
  2. 2. Download the Cisco NFVIS software upgrade from the official Cisco download portal (software.cisco.com) or obtain it through your Cisco support contract
  3. 3. Verify the integrity of the downloaded upgrade file using available cryptographic checksums provided by Cisco
  4. 4. Schedule a maintenance window for the upgrade procedure
  5. 5. Follow the standard Cisco NFVIS upgrade procedure documented in the Cisco Enterprise NFV Infrastructure Software administration guide
  6. 6. After upgrade, verify the system is running version 4.9.1 or later and confirm all services are operational
Caveat Review Cisco release notes for version 4.9.1 for any configuration or behavioral changes from previous versions; test in non-production environment first

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

Fix this in Enterprise Nfv Infrastructure Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20929 — 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-20929 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