Summary
Missing Role Based Access Control for the REST handlers in bleve/http package
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]].
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.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
CVE-2022-31022 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2022-31022? CVE-2022-31022 is a medium-severity missing authentication for critical function vulnerability in github.com/blevesearch/bleve (go), affecting versions <= 1.10.14. It is fixed in 2.5.0. A critical operation is accessible without requiring any authentication.
- How severe is CVE-2022-31022? CVE-2022-31022 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2022-31022?
github.com/blevesearch/bleve(go) (versions <= 1.10.14)github.com/blevesearch/bleve/v2(go) (versions < 2.5.0)
- Is there a fix for CVE-2022-31022? Yes. CVE-2022-31022 is fixed in 2.5.0. Upgrade to this version or later.
- Is CVE-2022-31022 exploitable, and should I be worried? Whether CVE-2022-31022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-31022 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-31022? Upgrade
github.com/blevesearch/bleve/v2to 2.5.0 or later.