How severe is CVE-2020-15170?

CVE-2020-15170 has a CVSS score of 7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-15170?

CVE-2020-15170 affects the following packages: com.ctrip.framework.apollo:apollo-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-15170?

Update com.ctrip.framework.apollo:apollo-core to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15170 is resolved across your whole dependency graph.

How do I detect CVE-2020-15170 in my Maven dependencies?

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2020-15170 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-15170 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-2020-15170?

CVE-2020-15170 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th 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.

What type of vulnerability is CVE-2020-15170?

CVE-2020-15170 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-15170 published, and has it been updated?

CVE-2020-15170 was published on September 10, 2020 and was last updated on August 27, 2026. 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

HIGH severity

CVE-2020-15170 — apollo-core

HIGHFix: ctripcorp/apollo#3233

CVE-2020-15170 is a high-severity (CVSS 7) Improper Input Validation vulnerability in com.ctrip.framework.apollo:apollo-core. A fix is available for com.ctrip.framework.apollo:apollo-core — see the affected versions and patch details below.

Potential access control security issue in apollo-adminservice

Also known asGHSA-xpmx-h7xq-xffh

Published

Sep 10, 2020

Updated

Aug 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-15170 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.ctrip.framework.apollo:apollo-core

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

Impact

If users expose apollo-adminservice to internet(which is not recommended), there are potential security issues since apollo-adminservice is designed to work in intranet and it doesn't have built-in access control. Malicious hackers may access apollo-adminservice apis directly to access/edit the application's configurations.

Patches

Access control for admin service was added in #3233 and was released in v1.7.1.

Workarounds

To fix the potential issue without upgrading, simply follow the advice that do not expose apollo-adminservice to internet.

Credits

Lexu reported the issue and provided the required information to reproduce it.

References

Apollo Security Guidence

For more information

If you have any questions or comments about this advisory:

Open an issue
Email to one of the active project maintainers

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.ctrip.framework.apollo:apollo-core`	all versions	1.7.1`com.ctrip.framework.apollo:apollo-core:1.7.1`

Affected Products

1 product · 1 configurations

Application

apolloctrip

< 1.7.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ctrip.framework.apollo:apollo-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.ctrip.framework.apollo:apollo-core to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15170 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact If users expose apollo-adminservice to internet(which is not recommended), there are potential security issues since apollo-adminservice is designed to work in intranet and it doesn't have built-in access control. Malicious hackers may access apollo-adminservice apis directly to access/edit the application's configurations. ### Patches Access control for admin service was added in #3233 and was released in [v1.7.1](https://github.com/ctripcorp/apollo/releases/tag/v1.7.1). ### Workarounds To fix the potential issue without upgrading, simply follow the advice that do not expose apol