CVE-2022-36312
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 software version 15.18.00.2511 lacks CSRF protections in the eNodeB's web management UI. 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 · moderate confidenceThe Airspan AirVelocity 1500 version 15.18.00.2511 web management UI for eNodeB devices lacks Cross-Site Request Forgery (CSRF) protection mechanisms. This allows remote attackers to trick authenticated administrators into unknowingly executing unwanted actions by crafting malicious requests that the victim's browser automatically sends with session credentials.
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= 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm device model is Airspan AirVelocity 1500Access the device's web management UI or check the device label/documentation to verify the exact model number is AirVelocity 1500.Affected if The device is not an Airspan AirVelocity 1500 unit.
-
Identify the installed firmware versionLog into the web management interface and navigate to the System, Status, or About page to view the firmware version. Alternatively, check via CLI or device documentation for version retrieval commands.Affected if The firmware version is 15.18.00.2511.
-
Verify the web management UI is accessibleAttempt to reach the device's web interface via its IP address in a browser. Confirm the login page loads.Affected if The web management UI is not exposed or not accessible.
-
Inspect forms for CSRF protection mechanismsLog into the web UI, navigate to a state-changing form (such as configuration or admin settings), view the page source or use browser developer tools to examine if the form includes anti-CSRF tokens, tokens in hidden fields, or checks for Origin/Referer headers.Affected if The forms lack anti-CSRF tokens or token validation logic in the page source.
You are affected if the device is an Airspan AirVelocity 1500 running firmware version 15.18.00.2511 with an accessible web management UI that lacks CSRF token protection on state-changing forms.
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 dataImplement anti-CSRF tokens on all state-changing forms and validate Origin/Referer headers server-side. Apply SameSite cookie attributes and consider implementing request confirmation for sensitive operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36312 — 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-36312 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