Missing Role Based Access Control for the REST handlers in bleve/http packageGHSA-9w9f-6mg8-jp7w
MEDIUMFix: blevesearch/bleve@1c7509dGHSA-9w9f-6mg8-jp7w is a medium-severity (CVSS 5.5) CWE-288 vulnerability in github.com/blevesearch/bleve. A fix is available for github.com/blevesearch/bleve — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9w9f-6mg8-jp7w.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/blevesearch/bleve🐹github.com/blevesearch/bleve/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
- Email us at [mailto:[email protected], [email protected]].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/blevesearch/bleve | all versions | No fix |
| 🐹Go | github.com/blevesearch/bleve/v2 | all versions | 2.5.0go get github.com/blevesearch/bleve/v2@v2.5.0 |
Affected Products
blevecouchbaseDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/blevesearch/bleve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-9w9f-6mg8-jp7w; check the affected-versions list above or the advisory for the patched release of github.com/blevesearch/bleve, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-9w9f-6mg8-jp7w in your dependencies?
Find it across Go, including transitive dependencies.