CVE-2015-5210 json
Apache Ambari Open Redirect
published 2015-11-02 11 y ago modified 2026-06-17 4 mo ago also GHSA-w3p6-94x2-xcvm , EUVD-2022-5481
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Open redirect vulnerability in Apache Ambari before 2.1.2 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the targetURI parameter.
Patch / fix
- maven org.apache.ambari:ambari 2.1.2
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-5210 updated cvss 5.8
Ambari: multiple flaws fixed in 2.1.2
-
Red Hat All currently supported Red Hat productsnot 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
4.12% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.ambari:ambari | >=1.7.0, <2.1.2 |
2.1.2 |
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
cwiki.apache.org
/confluence/display/AMBARI/Ambari+Vulnerabilities
vendor-advisory
-
openwall.com
/lists/oss-security/2015/10/13/4
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2015-5210
advisory
-
cwiki.apache.org
/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.1.2
web
Sources
- CVE List CVE-2015-5210
- GitHub Advisory GHSA-w3p6-94x2-xcvm
- NVD CVE-2015-5210
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.