GHSA-9w9f-6mg8-jp7w

Suggest an improvement
Source
https://github.com/advisories/GHSA-9w9f-6mg8-jp7w
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/06/GHSA-9w9f-6mg8-jp7w/GHSA-9w9f-6mg8-jp7w.json
JSON Data
https://api.test.osv.dev/v1/vulns/GHSA-9w9f-6mg8-jp7w
Aliases
Related
Published
2022-06-03T22:17:51Z
Modified
2024-09-11T06:12:25.372982Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
Summary
Missing Role Based Access Control for the REST handlers in bleve/http package
Details

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/indexcreate.go) and DeleteIndexHandler (http/indexdelete.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:security@couchbase.com, fts-team@couchbase.com].

Database specific
{
    "nvd_published_at": "2022-06-01T20:15:00Z",
    "github_reviewed_at": "2022-06-03T22:17:51Z",
    "severity": "MODERATE",
    "github_reviewed": true,
    "cwe_ids": [
        "CWE-306"
    ]
}
References

Affected packages

Go / github.com/blevesearch/bleve

Package

Name
github.com/blevesearch/bleve
View open source insights on deps.dev
Purl
pkg:golang/github.com/blevesearch/bleve

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Last affected
1.10.14

Go / github.com/blevesearch/bleve/v2

Package

Name
github.com/blevesearch/bleve/v2
View open source insights on deps.dev
Purl
pkg:golang/github.com/blevesearch/bleve/v2

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Last affected
2.3.6