How severe is CVE-2015-1775?

No CVSS score has been assigned to CVE-2015-1775 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-1775?

CVE-2015-1775 affects the following packages: org.apache.ambari:ambari (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-1775?

Update org.apache.ambari:ambari to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1775 is resolved across your whole dependency graph.

How do I detect CVE-2015-1775 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ambari:ambari, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-1775 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2015-1775 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-1775 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-1775?

CVE-2015-1775 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2015-1775 published, and has it been updated?

CVE-2015-1775 was published on May 17, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2015-1775 — ambari

CVE-2015-1775 is a security vulnerability in org.apache.ambari:ambari. A fix is available for org.apache.ambari:ambari — see the affected versions and patch details below.

Apache Ambari SSRF Vulnerability

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.ambari:ambari

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.ambari:ambari`	≥ 1.5.0&&< 2.1.0	2.1.0`org.apache.ambari:ambari:2.1.0`

Affected Products

1 product · 8 configurations

Application

ambariapache

8 versions

1.5.01.5.11.6.01.6.11.7.02.0.02.0.12.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ambari:ambari, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.ambari:ambari to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-1775 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2015-1775 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works