CVE-2023-25570: Apollo missing authentication in built-in Eureka service

CVE-2023-25570 · Severity: high · CVSS 7.5 · Published 2023-02-22

Apollo is a configuration management system used to manage application settings across environments. A security issue exists where the built-in service discovery component (Eureka) lacks authentication by default. If this service is exposed to the internet, unauthorized users could impersonate core Apollo services, potentially leading to the distribution of malicious configuration data to connected applications.

Technologies: ApolloConfig Apollo, com.ctrip.framework.apollo:apollo (Maven). Vendors: ApolloConfig, Maven.

Quick answers

Is CVE-2023-25570 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-25570 being exploited in the wild.
How severe is CVE-2023-25570?
High severity, with a CVSS score of 7.5, published 22 February 2023.
Which products and versions are affected?
ApolloConfig Apollo < 2.1.0; com.ctrip.framework.apollo:apollo (Maven) < 2.1.0, ECOSYSTEM:introduced=0,fixed=2.1.0.
Is there a fix for CVE-2023-25570?
Yes. com.ctrip.framework.apollo:apollo (Maven): upgrade to 2.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2023-25570 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2023-25570?
Check whether you run ApolloConfig Apollo or com.ctrip.framework.apollo:apollo (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • com.ctrip.framework.apollo:apollo (Maven): upgrade to 2.1.0 or later
    # set com.ctrip.framework.apollo:apollo to 2.1.0 in your pom.xml or build.gradle

Technical details

Apollo versions prior to 2.1.0 contain a missing authentication vulnerability (CWE-306) in the built-in Eureka service component. The root cause is that the `apollo-configservice` does not enforce credentials for Eureka interactions by default. A network-based attacker can access the Eureka registry without authentication to register rogue instances, effectively mocking the `apollo-configservice` and `apollo-adminservice`. This can be exploited to intercept or provide fraudulent configuration data to clients. The issue is mitigated by upgrading to version 2.1.0, which introduces login authentication for Eureka, or by ensuring the service is not reachable from the public internet.

Affected products

  • apolloconfig Apollo < 2.1.0

Identifiers

  • CVE-2023-25570
  • GHSA-368x-wmmg-hq5c

Timeline

  • 2022-11-26: other: Initial pull request created to add authentication
  • 2023-02-18: advisory: GitHub Advisory published
  • 2023-02-20: disclosed: NVD publication date
  • 2023-02-22: patched: Official release of version 2.1.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.