Security readout for executives and security teams
Plain-English summary
Bleve’s demonstration HTTP handlers were not built with access control. If a product exposed them, an unauthenticated actor could cause index directories to be created or deleted within the server user’s permitted filesystem area. The issue matters most where sample handlers became production management endpoints.
Executive priority
Prioritize review if Bleve powers a public or shared service. This is not a broad Bleve indexing flaw, but exposed demo handlers could enable destructive filesystem impact under the service account.
Technical view
CVE-2022-31022 affects blevesearch/bleve versions >=0.1.0 and <2.5.0 when applications use the bleve/http package to expose index access. The package lacks RBAC, authentication, authorization, and exhaustive input validation. The advisory names CreateIndexHandler and DeleteIndexHandler as risky handlers. Version 2.5.0 relocated the demo HTTP code to bleve-explorer.
Likely exposure
Exposure is limited to Go applications that imported bleve/http and mounted its handlers. Using Bleve as a library for indexing alone is not enough evidence of exposure.
Exploitation context
The bundle does not show active exploitation, and KEV is false. The CVSS vector is local, but the practical risk depends on whether an application exposed these handlers through an accessible HTTP service.
Researcher notes
The advisory frames bleve/http as demonstration-only and states Bleve was not designed to handle RBAC. Evidence supports exposure only where applications used those handlers without their own access controls. The bundle does not provide exploit prevalence or runtime detection indicators.
Mitigation direction
- Upgrade blevesearch/bleve to version 2.5.0 or later where feasible.
- Do not use bleve/http handlers in production services.
- Remove exposed index-management routes backed by bleve/http.
- Add explicit authentication and RBAC around any index administration endpoints.
- Restrict the service account’s filesystem permissions to necessary index paths only.
- Check current vendor guidance before choosing compensating controls.
Validation and detection
- Identify all projects using blevesearch/bleve versions below 2.5.0.
- Search code for imports of the bleve/http package.
- Review routing for mounted Bleve index create or delete handlers.
- Confirm no bleve/http endpoints are reachable from untrusted networks.
- Verify deployed service accounts cannot write or delete unnecessary directories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31022 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N2.53.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.2MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/blevesearch/bleve/security/advisories/GHSA-9w9f-6mg8-jp7wCVE reference · x_refsource_CONFIRM
- https://github.com/blevesearch/bleve/commit/1c7509d6a17d36f265c90b4e8f4e3a3182fe79ffCVE reference · x_refsource_MISC
- https://github.com/blevesearch/bleve/commit/af9e3111dadfedf9d30f0448506b4a57fecc8550CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.