Service-token disclosure via unauthenticated Eureka registration
Published Feb 20, 2023 · Updated Mar 10, 2025
Improper authorization in ApolloConfig Apollo before 2.1.0 allows remote attackers to steal service tokens via unauthenticated Eureka registration. The built-in Eureka registry accepts unauthenticated lease requests and adds attacker-controlled Config or Admin service instances to discovery. Network access to the ConfigService Tomcat endpoint and enabled service-token authentication let the rogue instance receive tokens from clients.
Summary
What happened
Improper authorization in ApolloConfig Apollo before 2.1.0 allows remote attackers to steal service tokens via unauthenticated Eureka registration. The built-in Eureka registry accepts unauthenticated lease requests and adds attacker-controlled Config or Admin service instances to discovery. Network access to the ConfigService Tomcat endpoint and enabled service-token authentication let the rogue instance receive tokens from clients.
The record
- CVE
- CVE-2023-25570
- Published
- Feb 20, 2023
- Updated
- Mar 10, 2025
- Vendor
- ApolloConfig
- Product
- Apollo
- Classifications
- CWE-306, T1190, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2023CVE publishedPublication date reported by the CVE source.
- Mar 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub Security Lab rogue Eureka instance proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo