Security readout for executives and security teams
CVE-2014-3120 is a legacy Elasticsearch risk where older default settings allowed search requests to run server-side scripts. If an affected Elasticsearch service was reachable by an attacker, that could become code execution on the Elasticsearch host. CISA KEV lists it as known exploited, so any remaining exposure deserves urgent removal. Exposure is most likely in old Elasticsearch deployments before 1.2, embedded products using that stack, or internet-accessible search clusters left reachable without strong isolation. The bundle does not identify specific downstream affected products beyond Elasticsearch. Treat as urgent for legacy environments. The issue is old, but KEV status and public exploit references mean any surviving exposed instance is a credible business risk. Mitigation focus: Identify and retire Elasticsearch versions before 1.2.; Follow Elastic security guidance for supported upgrade and configuration paths.; Disable dynamic scripting where vendor guidance supports doing so..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2014-3120 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.elastic.co/blog/logstash-1-4-3-releasedCVE reference · x_refsource_CONFIRM
- https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearchCVE reference · x_refsource_MISC
- https://www.elastic.co/community/security/CVE reference · x_refsource_CONFIRM
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-3120CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.