CVE-2022-36308
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 · uneditedAirspan AirVelocity 1500 web management UI displays SNMP credentials in plaintext on software versions older than 15.18.00.2511, and stores SNMPv3 credentials unhashed on the filesystem, enabling anyone with web access to use these credentials to manipulate the eNodeB over SNMP. This issue 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 Airspan AirVelocity 1500 web management UI exposes SNMP credentials in plaintext on versions prior to 15.18.00.2511, and stores SNMPv3 credentials unhashed on the filesystem. An attacker with web access can retrieve these plaintext credentials and use them to authenticate to the device's SNMP service, enabling manipulation of the eNodeB (evolved Node B) base station.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Airspan AirVelocity 1500Identify the hardware by checking the device label, web interface header, or SNMP system description. Compare the model number to the affected product list.Affected if The device is an Airspan AirVelocity 1500 unit.
-
Determine installed firmware versionAccess the web management UI and navigate to the firmware or status page to view the running version, or use SNMP or CLI commands to query the firmware revision. Compare the version number against the affected range of >= 9.3.0.01249 and <= 15.18.00.2511.Affected if The firmware version falls within 9.3.0.01249 through 15.18.00.2511 inclusive.
-
Verify web management interface is exposedDetermine if the web management UI port (typically HTTP/HTTPS on port 80/443 or custom ports) is reachable from untrusted networks. Check network segmentation, firewall rules, and ACLs restricting management access.Affected if The web management interface is accessible from networks beyond trusted administration segments.
-
Inspect for plaintext SNMP credential exposureIf web access is available, examine the SNMP configuration pages within the web management UI for any credentials displayed in plaintext. Also check the filesystem or configuration backups for SNMPv3 credential files stored in unhashed form.Affected if SNMP community strings or SNMPv3 credentials are visible in the web UI configuration pages or found stored in plaintext/unhashed format on the device filesystem.
The environment is affected if the device is an Airspan AirVelocity 1500 running firmware version 9.3.0.01249 through 15.18.00.2511 with its web management interface accessible and SNMP credentials exposed in plaintext or stored unhashed.
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.
dbcve · scopedUpgrade AirVelocity 1500 firmware to version 15.18.00.2511 or later. If immediate patching is not possible, restrict web management interface access to trusted networks via firewall rules and implement SNMP access monitoring/alerts.
Airspan AirVelocity 1500 Firmware >= 15.18.00.2511
- Identify the current firmware version of the AirVelocity 1500 device via the web management UI or CLI
- Download the Airspan firmware version 15.18.00.2511 or a later stable release from the official Airspan helpdesk (helpdesk.airspan.com) or authorized support channels
- Review the firmware upgrade instructions in the Airspan official documentation to ensure proper upgrade procedure
- Initiate the firmware upgrade through the device's web management interface or appropriate upgrade mechanism
- After upgrade, verify the device firmware version has been successfully updated to 15.18.00.2511 or later
- Log into the web management UI and confirm that SNMP credentials are no longer displayed in plaintext
- Verify that SNMPv3 credentials are now stored in a hashed format on the filesystem if accessible
- Test SNMP functionality to ensure the eNodeB operates correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36308 — 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-36308 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