AmbariApplication · Apache
CVE-2015-1775
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedServer-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Ambari versions before 2.1.0 contain an SSRF vulnerability in the api/v1/proxy endpoint. Authenticated users can craft REST calls to make the server perform arbitrary HTTP requests, enabling port scanning of internal services and access to unsecured internal resources that should not be exposed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AmbariApplication
= 1.5.0= 1.5.1= 1.6.0= 1.6.1= 1.7.0= 2.0.0= 2.0.1= 2.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ambari versionCheck the Ambari server version by querying the Ambari REST API endpoint /api/v1/version, or inspect the Ambari server logs at /var/log/ambari-server/ambari-server.log for the version string at startup, or run 'ambari-server version' if the CLI is available.Affected if The installed version is 1.5.0, 1.5.1, 1.6.0, 1.6.1, 1.7.0, 2.0.0, 2.0.1, or 2.0.2.
-
Verify the proxy endpoint existsConfirm the api/v1/proxy endpoint is present by attempting a GET request to http://<ambari-host>:8080/api/v1/proxy. The endpoint should return a response (typically a 400 or 405 error indicating the endpoint is recognized but method not allowed, rather than a 404).Affected if The endpoint returns any response other than 404 Not Found, indicating the proxy functionality is present.
-
Check if proxy endpoint accepts requestsSend a POST request to /api/v1/proxy with a JSON body containing a target URL, such as {"URL":"http://localhost:22"} or similar, and observe if the server attempts to fetch or connect to the specified URL.Affected if The server processes the request and returns results from the specified URL, confirming the SSRF vulnerability is present.
You are affected if your Ambari version is 2.0.2 or earlier (1.5.0 through 2.0.2) and the api/v1/proxy endpoint accepts and processes requests to arbitrary URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Apache Ambari 2.1.0 or later, which contains the fix. If immediate upgrade is not possible, restrict access to the proxy endpoint via network segmentation or authentication controls.
Fix this in Ambari
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data