Summary
apollo-portal has potential unauthorized access issue
Workarounds
To mitigate the issue without upgrading, follow the recommended practices to prevent Apollo from being exposed to the internet.
Credits
The vulnerability was reported and reproduced by Lakeswang.
References
For any questions or comments regarding this advisory:
- Open an issue in issue
- Email us at [email protected]
Impact
A vulnerability exists in the synchronization configuration feature that allows users to craft specific requests to bypass permission checks. This exploit enables them to modify a namespace without the necessary permissions.
CVE-2024-43397 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low 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 (2.3.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
The issue was addressed with an input parameter check in #5192, which was released in version 2.3.0.
Frequently Asked Questions
- What is CVE-2024-43397? CVE-2024-43397 is a medium-severity security vulnerability in com.ctrip.framework.apollo:apollo (maven), affecting versions < 2.3.0. It is fixed in 2.3.0.
- How severe is CVE-2024-43397? CVE-2024-43397 has a CVSS score of 4.3 (Medium). 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 are affected by CVE-2024-43397? com.ctrip.framework.apollo:apollo (maven) versions < 2.3.0 is affected.
- Is there a fix for CVE-2024-43397? Yes. CVE-2024-43397 is fixed in 2.3.0. Upgrade to this version or later.
- Is CVE-2024-43397 exploitable, and should I be worried? Whether CVE-2024-43397 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-2024-43397 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-2024-43397? Upgrade
com.ctrip.framework.apollo:apolloto 2.3.0 or later.