LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45855: Apache Ambari: Allows authenticated metrics consumers to perform RCE

SpringEL injection in the metrics source in Apache Ambari version 2.7.0 to 2.7.6 allows a malicious authenticated user to execute arbitrary code remotely. Users are recommended to upgrade to 2.7.7.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apache Ambari 2.7.0 through 2.7.6 has a Spring Expression Language injection flaw in its metrics source. A logged-in, malicious user with metrics consumer access could run code remotely. This is high business risk where Ambari manages production Hadoop or big-data infrastructure. Apache recommends upgrading to 2.7.7.

Executive priority

Prioritize remediation for internet-reachable, broadly accessible, or production Ambari deployments. Treat this as a high-risk authenticated RCE issue, but do not claim active exploitation from the provided evidence.

Technical view

CVE-2022-45855 is CWE-917 SpringEL injection in Apache Ambari's metrics source. The CVSS 3.1 score is 8.0, with network attack vector, low complexity, low privileges, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in environments running Apache Ambari 2.7.0 to 2.7.6 with authenticated users able to consume metrics. The provided affected metadata is sparse, so teams should verify installed Ambari versions directly against Apache guidance.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability still matters because authenticated access can become remote code execution, especially in shared operations environments with many Ambari users.

Researcher notes

The public details identify SpringEL injection in the metrics source but do not provide deep technical root cause or exploit telemetry. The CVSS vector includes user interaction required; preserve that nuance when modeling exploitability.

Mitigation direction

  • Upgrade Apache Ambari to version 2.7.7, as recommended by Apache.
  • Inventory all Ambari servers and confirm no 2.7.0 to 2.7.6 deployments remain.
  • Review and reduce metrics consumer access to necessary authenticated users only.
  • Check Apache vendor guidance for any additional environment-specific hardening.

Validation and detection

  • Confirm the deployed Ambari version on every management host.
  • Map Ambari users and groups with metrics consumer permissions.
  • Review logs for unusual authenticated metrics activity without assuming confirmed exploitation.
  • Verify change records show upgrade completion to Ambari 2.7.7.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-917: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-45855 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H2.15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2022-45855Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Ambari2.7.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-917 · source CWE mapping

Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')

Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.