Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Missing Role Based Access Control for the REST handlers in bleve/http package

CVSS 3.1 6.2 MEDIUMEUVD CVSS 3.1 6.2 CVSS 3.1 · [email protected] · Secondary 6.2 MEDIUMCVSS 3.1 · [email protected] · Primary 5.5 MEDIUMCVSS 2.0 · [email protected] · Primary 2.1 LOWCVSS_V3 Publisher rating MODERATEFixed by github.com/blevesearch/bleve/v2 2.5.0osv · severity unknownFixed by github.com/blevesearch/bleve/v2 2.5.0KEV status unknown

cve-program · CVE-2022-31022

Published

Bleve is a text indexing library for go. Bleve includes HTTP utilities under bleve/http package, that are used by its sample application. These HTTP methods pave way for exploitation of a node’s filesystem where the bleve index resides, if the user has used bleve’s own HTTP (bleve/http) handlers for exposing the access to the indexes. For instance, the CreateIndexHandler (`http/index_create.go`) and DeleteIndexHandler (`http/index_delete.go`) enable an attacker to create a bleve index (directory structure) anywhere where the user running the server has the write permissions and to delete recursively any directory owned by the same user account. Users who have used the bleve/http package for exposing access to bleve index without the explicit handling for the Role Based Access Controls(RBAC) of the index assets would be impacted by this issue. Version 2.5.0 relocated the `http/` dir used _only_ by bleve-explorer to `blevesearch/bleve-explorer`, thereby addressing the issue. However, the http package is purely intended to be used for demonstration purposes. Bleve was never designed handle the RBACs, nor it was ever advertised to be used in that way. The collaborators of this project have decided to stay away from adding any authentication or authorization to bleve project at the moment. The bleve/http package is mainly for demonstration purposes and it lacks exhaustive validation of the user inputs as well as any authentication and authorization measures. It is recommended to not use bleve/http in production use cases.

Read the publisher's advisory

euvd · EUVD-2022-6017

Published

Bleve is a text indexing library for go. Bleve includes HTTP utilities under bleve/http package, that are used by its sample application. These HTTP methods pave way for exploitation of a node’s filesystem where the bleve index resides, if the user has used bleve’s own HTTP (bleve/http) handlers for exposing the access to the indexes. For instance, the CreateIndexHandler (`http/index_create.go`) and DeleteIndexHandler (`http/index_delete.go`) enable an attacker to create a bleve index (directory structure) anywhere where the user running the server has the write permissions and to delete recursively any directory owned by the same user account. Users who have used the bleve/http package for exposing access to bleve index without the explicit handling for the Role Based Access Controls(RBAC) of the index assets would be impacted by this issue. Version 2.5.0 relocated the `http/` dir used _only_ by bleve-explorer to `blevesearch/bleve-explorer`, thereby addressing the issue. However, the http package is purely intended to be used for demonstration purposes. Bleve was never designed handle the RBACs, nor it was ever advertised to be used in that way. The collaborators of this project have decided to stay away from adding any authentication or authorization to bleve project at the moment. The bleve/http package is mainly for demonstration purposes and it lacks exhaustive validation of the user inputs as well as any authentication and authorization measures. It is recommended to not use bleve/http in production use cases.

Read the publisher's advisory

nvd · CVE-2022-31022

Published

Bleve is a text indexing library for go. Bleve includes HTTP utilities under bleve/http package, that are used by its sample application. These HTTP methods pave way for exploitation of a node’s filesystem where the bleve index resides, if the user has used bleve’s own HTTP (bleve/http) handlers for exposing the access to the indexes. For instance, the CreateIndexHandler (`http/index_create.go`) and DeleteIndexHandler (`http/index_delete.go`) enable an attacker to create a bleve index (directory structure) anywhere where the user running the server has the write permissions and to delete recursively any directory owned by the same user account. Users who have used the bleve/http package for exposing access to bleve index without the explicit handling for the Role Based Access Controls(RBAC) of the index assets would be impacted by this issue. Version 2.5.0 relocated the `http/` dir used _only_ by bleve-explorer to `blevesearch/bleve-explorer`, thereby addressing the issue. However, the http package is purely intended to be used for demonstration purposes. Bleve was never designed handle the RBACs, nor it was ever advertised to be used in that way. The collaborators of this project have decided to stay away from adding any authentication or authorization to bleve project at the moment. The bleve/http package is mainly for demonstration purposes and it lacks exhaustive validation of the user inputs as well as any authentication and authorization measures. It is recommended to not use bleve/http in production use cases.

Read the publisher's advisory

osv · GHSA-9w9f-6mg8-jp7w

Published

### Impact _What kind of vulnerability is it? Who is impacted?_ Bleve includes HTTP utilities under bleve/http package, that are used by its sample application. (https://github.com/blevesearch/bleve-explorer) These HTTP methods paves way for exploitation of a node’s filesystem where the bleve index resides, if the user has used bleve’s own HTTP (bleve/http) handlers for exposing the access to the indexes. For instance, the CreateIndexHandler (http/index_create.go) and DeleteIndexHandler (http/index_delete.go) enable an attacker to create a bleve index (directory structure) anywhere where the user running the server has the write permissions and to delete recursively any directory owned by the same user account. Users who have used the bleve/http package for exposing access to bleve index without the explicit handling for the Role Based Access Controls(RBAC) of the index assets would be impacted. ### Patches _Has the problem been patched? What versions should users upgrade to?_ **No**. The http package is purely intended to be used for demonstration purposes. And bleve is never designed to be handling the RBACs or it was ever advertised to be used in that way. Hence the collaborators of this project have decided to stay away from adding any authentication or authorization to bleve project at the moment. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ The bleve/http package is mainly for demonstration purposes and it lacks exhaustive validation of the user inputs as well as any authentication and authorization measures. So it is recommended to not use that in production use cases. ### For more information If you have any questions or comments about this advisory: * Open an issue [here](https://github.com/blevesearch/bleve/issues). * Email us at [mailto:[email protected], [email protected]].

Read the publisher's advisory

osv · GO-2022-0470

Published

HTTP handlers provide unauthenticated access to the local filesystem. The Bleve http package is intended for demonstration purposes and contains no authentication, authorization, or validation of user inputs. Exposing handlers from this package can permit attackers to create files and delete directories.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2022-31022

Published

bleve

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "blevesearch",
                    "product": "bleve",
                    "versions": [
                        {
                            "version": ">= 0.1.0, < 2.5.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2022-6017

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jun 1, 2022, 7:45:12 PM

dateUpdated: May 8, 2025, 1:44:47 PM

1 related source bulletins · separate from aliases

openSUSE-SU-2025:15225-1: govulncheck-vulndb-0.0.20250612T141001-1.1 on GA media

CVE-2020-36846 · CVE-2022-31022 · CVE-2023-42818 · CVE-2025-0913 · CVE-2025-1792 · CVE-2025-22874 · CVE-2025-25207 · CVE-2025-25208 · CVE-2025-2571 · CVE-2025-29785 · CVE-2025-3230 · CVE-2025-3260 · CVE-2025-3454 · CVE-2025-3611 · CVE-2025-3913 · CVE-2025-4128 · CVE-2025-4573 · CVE-2025-4673 · CVE-2025-47950 · CVE-2025-48494 · CVE-2025-48495 · CVE-2025-48710 · CVE-2025-48865 · CVE-2025-48938 · CVE-2025-48948 · CVE-2025-48949 · CVE-2025-49011 · CVE-2025-49136 · CVE-2025-49140

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2022-31022

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-288 · CWE-306

Original publisher date fields

published: 2022-06-01T20:15:08.037

lastModified: 2026-06-17T04:44:37.473

1 source CPE criteria · context only
  • cpe:2.3:a:couchbase:bleve:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-9w9f-6mg8-jp7w

Published

github.com/blevesearch/bleve

Go

SEMVER · introduced 0 → last_affected 1.10.14

github.com/blevesearch/bleve/v2

Go

SEMVER · introduced 0 → fixed 2.5.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2022-0470

Published

github.com/blevesearch/bleve

Go

SEMVER · introduced 0

github.com/blevesearch/bleve/v2

Go

SEMVER · introduced 0 → fixed 2.5.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current