CVE-2022-34331
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 · uneditedAfter performing a sequence of Power FW950, FW1010 maintenance operations a SRIOV network adapter can be improperly configured leading to desired VEPA configuration being disabled. IBM X-Force ID: 229695.
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 confidenceA sequence of Power firmware maintenance operations (FW950, FW1010) can cause SRIOV network adapters to become improperly configured, resulting in the intended VEPA (Virtual Ethernet Port Aggregator) configuration being disabled. This configuration drift could allow unintended network traffic behavior or bypass expected network segmentation.
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= fw950= fw1010CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Power firmware versionRun `lsmcode -c` or `lslic -c` to display the current firmware version. Compare the output to fw950 or fw1010.Affected if The firmware version shown is exactly fw950 or fw1010
-
Identify SRIOV network adaptersRun `lsdev -type adapter | grep -i sriov` or `lsslot -c slot | grep -i sriov` to list configured SRIOV adapters.Affected if SRIOV network adapters are present in the system output
-
Verify VEPA configuration on SRIOV adaptersFor each SRIOV adapter, run `lsattr -El <adapter> | grep -i vepa` to check the VirtualEthernetPortAggregator attribute. Alternatively, query each virtual ethernet port with `lsattr -El entX | grep vepa`.Affected if The vepa attribute shows as disabled, not configured, or the output shows a mismatch from the expected VEPA enabled state
-
Check for configuration drift after firmware updatesCompare current SRIOV adapter configuration against documented baseline or expected configuration. Use `lsattr -El <adapter>` before and after firmware maintenance to detect changes.Affected if The current configuration differs from the intended VEPA configuration, or VEPA was previously enabled but is now disabled
A system is affected if it runs IBM PowerVM firmware fw950 or fw1010, has SRIOV network adapters configured, and the VEPA configuration is disabled or has drifted from the intended state.
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 dataApply subsequent IBM Power firmware updates that address this configuration drift issue, and verify/re-apply VEPA configuration settings after any firmware maintenance operations on affected systems.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34331 — 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-34331 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