Skip to content
Fencer Intel
medium 5.5

CVE-2015-1775 json

Apache Ambari SSRF Vulnerability

published 11y ago modified 4mo ago also GHSA-9g2j-5685-h44h , EUVD-2022-3368

cvss
5.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.0%
EPSS 3.0% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

Server-side request forgery (SSRF) vulnerability in the proxy endpoint (api/v1/proxy) in Apache Ambari before 2.1.0 allows remote authenticated users to conduct port scans and access unsecured services via a crafted REST call.

Patch / fix

  • maven org.apache.ambari:ambari 2.1.0

Is CVE-2015-1775 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-1775 updated cvss 5.8

Ambari: multiple flaws fixed in 2.1.2

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.95% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.ambari:ambari
>=1.5.0, <2.1.0
2.1.0

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.