# CVE-2019-10686: Server-Side Request Forgery (SSRF) in com.ctrip.framework.apollo:apollo

> An attacker can exploit an SSRF vulnerability in the Apollo configuration library to perform intranet port scans or trigger GET requests.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fvx3-g627-phm2

## What is CVE-2019-10686?

CVE-2019-10686 is a critical server-side request forgery vulnerability in n/a, published on 1 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SSRF vulnerability was found in an API from Ctrip Apollo through 1.4.0-SNAPSHOT. An attacker may use it to do an intranet port scan or raise a GET request via /system-info/health because the %23 substring is mishandled.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-10686?

2 open source packages ship an affected version, including com.ctrip.framework.apollo:apollo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.ctrip.framework.apollo:apollo` | Maven | All versions to 1.3.0 | None |
| `com.ctrip.framework.apollo:apollo` | Maven | All versions to 1.3.0 | None |

Products: Ctrip Apollo.

## How do I fix CVE-2019-10686?

No fix has been published for CVE-2019-10686 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-10686 being exploited?

There is no known exploitation of CVE-2019-10686 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-15170](https://insights.sbomify.com/CVE-2020-15170/): Missing access control in apollo-adminservice (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10686 and fix it if it is affected.

What it is: CVE-2019-10686 is a critical server-side request forgery vulnerability in n/a, published on 1 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10686 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.ctrip.framework.apollo:apollo (Maven): affected all versions up to 1.3.0; no fix listed
- com.ctrip.framework.apollo:apollo (Maven): affected all versions up to 1.3.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-10686/ (Markdown: https://insights.sbomify.com/CVE-2019-10686/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10686
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10686
- OSV: https://osv.dev/vulnerability/CVE-2019-10686

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-10686/
Summaries are generated and may contain mistakes; the official description above is the record.
