ghsa-mrfm-jxgf-2h6v
Vulnerability from github
Published
2022-05-17 03:28
Modified
2025-01-06 22:28
Summary
Elasticsearch Improper Access Control vulnerability
Details
The default configuration in Elasticsearch before 1.4.0.Beta1 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.
{ affected: [ { package: { ecosystem: "Maven", name: "org.elasticsearch:elasticsearch", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "1.4.0.Beta1", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2014-3120", ], database_specific: { cwe_ids: [ "CWE-284", ], github_reviewed: true, github_reviewed_at: "2025-01-06T22:28:40Z", nvd_published_at: "2014-07-28T19:55:00Z", severity: "MODERATE", }, details: "The default configuration in Elasticsearch before 1.4.0.Beta1 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.", id: "GHSA-mrfm-jxgf-2h6v", modified: "2025-01-06T22:28:40Z", published: "2022-05-17T03:28:58Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2014-3120", }, { type: "WEB", url: "https://github.com/elastic/elasticsearch/issues/7151", }, { type: "WEB", url: "https://github.com/elastic/elasticsearch/pull/7642", }, { type: "WEB", url: "https://github.com/elastic/elasticsearch/commit/bd0eb32d9c3c3f5b6e5f8630c859cd04bdcd4e06", }, { type: "WEB", url: "https://github.com/elastic/elasticsearch/commit/f9de8b65898509e038e33215db0720b508477a12", }, { type: "PACKAGE", url: "https://github.com/elastic/elasticsearch", }, { type: "WEB", url: "https://web.archive.org/web/20140813071419/http://www.securityfocus.com/bid/67731", }, { type: "WEB", url: "https://www.elastic.co/blog/logstash-1-4-3-released", }, { type: "WEB", url: "https://www.elastic.co/community/security", }, { type: "WEB", url: "https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearch", }, { type: "WEB", url: "http://bouk.co/blog/elasticsearch-rce", }, { type: "WEB", url: "http://www.exploit-db.com/exploits/33370", }, { type: "WEB", url: "http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/script_mvel_rce", }, ], schema_version: "1.4.0", severity: [], summary: "Elasticsearch Improper Access Control vulnerability", }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.