CVE-2022-39184
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 · uneditedEXFO - BV-10 Performance Endpoint Unit authentication bypass User can manually manipulate access enabling authentication bypass.
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 confidenceThe EXFO BV-10 Performance Endpoint Unit contains an authentication bypass vulnerability allowing unauthenticated users to manually manipulate access controls and gain unauthorized access to the device. This critical flaw enables attackers to bypass authentication mechanisms entirely, potentially exposing sensitive network testing functionality and configuration 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 dataall versionsCVSS 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.
-
Identify EXFO BV-10 device on networkCheck device model/version via SNMP, HTTP management interface, or network scanning for EXFO BV-10 fingerprintsAffected if Device is confirmed as an EXFO BV-10 Performance Endpoint Unit and is running any firmware version
-
Verify network exposure of management interfaceReview firewall rules, ACLs, and network segmentation to determine if the BV-10 management interface (typically HTTP/HTTPS on ports 80/443 or custom ports) is accessible from untrusted networks or the internetAffected if Management interface is reachable from networks outside trusted management segments
-
Check for unauthorized configuration changesCompare current device configuration against known-good baselines, specifically examining access control lists, user accounts, and authentication settings for unexpected modificationsAffected if Configuration shows unauthorized accounts, modified ACLs, or disabled authentication mechanisms
-
Look for signs of unauthorized accessReview device logs, authentication logs, and audit trails for successful or attempted access from unexpected IP addresses, especially during periods when no legitimate admin was logged inAffected if Logs show authentication bypass events, unexplained admin sessions, or access from unknown sources
If the device is an EXFO BV-10 with any firmware version and its management interface is accessible from untrusted networks, the environment is affected by this vulnerability.
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 vendor-supplied firmware patches immediately. Until a patch is available, restrict network access to the BV-10 device using network segmentation and firewall rules to limit exposure to trusted management networks only.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39184 — 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-39184 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