What is CVE-2020-15170?

CVE-2020-15170 is a high-severity improper input validation vulnerability in com.ctrip.framework.apollo:apollo-core (maven), affecting versions < 1.7.1. It is fixed in 1.7.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2020-15170?

CVE-2020-15170 has a CVSS score of 7.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.ctrip.framework.apollo:apollo-core are affected by CVE-2020-15170?

com.ctrip.framework.apollo:apollo-core (maven) versions < 1.7.1 is affected.

Is there a fix for CVE-2020-15170?

Yes. CVE-2020-15170 is fixed in 1.7.1. Upgrade to this version or later.

Is CVE-2020-15170 exploitable, and should I be worried?

Whether CVE-2020-15170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-15170 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-15170?

Upgrade com.ctrip.framework.apollo:apollo-core to 1.7.1 or later.

CVE-2020-15170

Q: How severe is CVE-2020-15170?

CVE-2020-15170 has a CVSS score of 7.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.ctrip.framework.apollo:apollo-core are affected by CVE-2020-15170?

com.ctrip.framework.apollo:apollo-core (maven) versions < 1.7.1 is affected.

Q: Is there a fix for CVE-2020-15170?

Yes. CVE-2020-15170 is fixed in 1.7.1. Upgrade to this version or later.

Q: Is CVE-2020-15170 exploitable, and should I be worried?

Whether CVE-2020-15170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-15170 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-15170?

Upgrade com.ctrip.framework.apollo:apollo-core to 1.7.1 or later.

Summary

Potential access control security issue in apollo-adminservice

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

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2020-15170 has a CVSS score of 7.0 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.1); upgrading removes the vulnerable code path.

Affected versions

com.ctrip.framework.apollo:apollo-core (< 1.7.1)

Security releases

com.ctrip.framework.apollo:apollo-core → 1.7.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2020-15170? CVE-2020-15170 is a high-severity improper input validation vulnerability in com.ctrip.framework.apollo:apollo-core (maven), affecting versions < 1.7.1. It is fixed in 1.7.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2020-15170? CVE-2020-15170 has a CVSS score of 7.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.ctrip.framework.apollo:apollo-core are affected by CVE-2020-15170? com.ctrip.framework.apollo:apollo-core (maven) versions < 1.7.1 is affected.
Is there a fix for CVE-2020-15170? Yes. CVE-2020-15170 is fixed in 1.7.1. Upgrade to this version or later.
Is CVE-2020-15170 exploitable, and should I be worried? Whether CVE-2020-15170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-15170 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-15170? Upgrade com.ctrip.framework.apollo:apollo-core to 1.7.1 or later.