dbcve.org
Vector Packet ProcessorApplication · Lfprojects

CVE-2022-46397

HIGH · 7.5 CVSS v3.1 Published 2023-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
FP.io VPP (Vector Packet Processor) 22.10, 22.06, 22.02, 21.10, 21.06, 21.01, 20.09, 20.05, 20.01, 19.08, and 19.04 Generates a Predictable IV with CBC Mode.

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

VPP (Vector Packet Processor) versions 22.10, 22.06, 22.02, 21.10, 21.06, 21.01, 20.09, 20.05, 20.01, 19.08, and 19.04 use predictable Initialization Vectors (IVs) when operating in CBC mode encryption. This cryptographic weakness allows attackers to potentially recover plaintext or perform chosen-plaintext attacks, compromising confidentiality of encrypted traffic.

MitigationReplace predictable IV generation with cryptographically secure random IVs for all CBC mode encryption operations, or migrate to authenticated encryption modes like GCM that provide built-in IV handling.

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
Vector Packet ProcessorApplication
Affected:= 19.04= 19.08= 20.01= 20.05= 20.09= 21.01= 21.06= 21.10= 22.02= 22.06= 22.10

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

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

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

  1. Confirm VPP installation
    Run 'vpp -v' or 'vppctl -v' to check if VPP is installed and get version information
    Affected if Version matches any of: 19.04, 19.08, 20.01, 20.05, 20.09, 21.01, 21.06, 21.10, 22.02, 22.06, or 22.10
  2. Identify VPP process and binary location
    Run 'ps aux | grep vpp' or 'which vpp' to locate the VPP binary
    Affected if VPP binary exists and version cannot be determined or matches affected versions
  3. Check for CBC mode encryption configuration
    Inspect VPP configuration files in /etc/vpp/ or examine running config via 'vppctl show crypto' to identify if CBC encryption is enabled
    Affected if CBC mode encryption is configured or in use
  4. Verify IV generation behavior
    Review VPP logs or capture traffic to observe if IVs follow predictable patterns across encryption operations
    Affected if IVs appear sequential, zero-based, or otherwise predictable rather than cryptographically random

If VPP version is one of the listed affected versions AND CBC mode encryption is in use, the environment is vulnerable to CVE-2022-46397

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

Replace predictable IV generation with cryptographically secure random IVs for all CBC mode encryption operations, or migrate to authenticated encryption modes like GCM that provide built-in IV handling.

Recommended fix Moderate confidence

VPP 22.10.01 or later stable release (versions after 22.10 contain the fix)

  1. 1. Identify the current VPP version installed using 'vpp -v' or checking the package manager
  2. 2. Plan maintenance window as upgrade may require service interruption
  3. 3. Backup current VPP configuration before upgrade
  4. 4. For Debian/Ubuntu: Run 'apt-get update && apt-get upgrade' or upgrade specific package
  5. 5. For RHEL/CentOS: Run 'yum update' or 'dnf update'
  6. 6. For containerized deployments: Update container image to fixed version and restart containers
  7. 7. Verify VPP starts successfully after upgrade
  8. 8. Test that affected cryptographic functionality works correctly
Caveat Minor: Verify custom plugins are compatible with newer VPP release; some CLI outputs may have changed format

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

Fix this in Vector Packet Processor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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