CVE-2022-36307
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 · uneditedThe AirVelocity 1500 prints SNMP credentials on its physically accessible serial port during boot. This was fixed in AirVelocity 1500 software version 15.18.00.2511 and may affect other AirVelocity and AirSpeed models.
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 confidenceThe AirVelocity 1500 (and possibly other AirVelocity/AirSpeed models) exposes SNMP community string credentials on its physically accessible serial console during the boot process. An attacker with physical access to the device's serial port can capture these credentials during boot, enabling unauthorized access to the device's SNMP management interface.
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>= 9.3.0.01249, <= 15.18.00.2511CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 the device modelPhysically inspect the device or check SNMP sysDescr for 'AirVelocity 1500' or 'Airspan' brandingAffected if Device is not an AirVelocity 1500 (other models may have different version ranges)
-
Check firmware version via SNMPQuery SNMP OID 1.3.6.1.2.1.47.1.1.1.1.10.1 (entPhysicalSoftwareRev) or use 'snmpget' command: snmpget -v2c -c <community> <device_ip> 1.3.6.1.2.1.47.1.1.1.1.10.1Affected if Cannot retrieve firmware version via SNMP
-
Compare firmware version to affected rangeParse the firmware version string retrieved from SNMP or serial console and compare numerically against 9.3.0.01249 (min) and 15.18.00.2511 (max)Affected if Firmware version is greater than or equal to 9.3.0.01249 AND less than or equal to 15.18.00.2511
-
Verify serial console is accessibleInspect physical location of device to determine if serial port (DB-9 or RJ-45) is in an area with uncontrolled physical accessAffected if Serial port is physically accessible to unauthorized personnel (this is required for exploitation but version check alone determines CVE applicability)
If the device is an AirVelocity 1500 running firmware between versions 9.3.0.01249 and 15.18.00.2511, the environment is affected by this CVE.
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 dataUpgrade AirVelocity 1500 to software version 15.18.00.2511 or later. Until patched, restrict physical access to the serial port and consider changing any SNMP credentials that may have been exposed.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36307 — 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-36307 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