Credential exposure via packaged user settings
Published Sep 26, 2024 · Updated Mar 17, 2025
Information exposure in Apache Maven Archetype Plugin 3.2.1 allows remote attackers to retrieve published artifacts containing Maven settings. IntegrationTestMojo writes the complete user settings model to target/classes/archetype-it/archetype-settings.xml, placing it in packaged class output on a later build. Exposure requires integration testing, a later mvn verify without mvn clean, and publication of the resulting artifact; disclosed data includes repository credentials stored in settings.xml.
Summary
What happened
Information exposure in Apache Maven Archetype Plugin 3.2.1 allows remote attackers to retrieve published artifacts containing Maven settings. IntegrationTestMojo writes the complete user settings model to target/classes/archetype-it/archetype-settings.xml, placing it in packaged class output on a later build. Exposure requires integration testing, a later mvn verify without mvn clean, and publication of the resulting artifact; disclosed data includes repository credentials stored in settings.xml.
The record
- CVE
- CVE-2024-47197
- Published
- Sep 26, 2024
- Updated
- Mar 17, 2025
- Vendor
- The Apache Software Foundation
- Product
- Maven Archetype Plugin
- Classifications
- CWE-922, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2024CVE publishedPublication date reported by the CVE source.
- Mar 17, 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=3.2.1 <3.3.0
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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