GHSA-2qq7-fch2-phqf

Suggest an improvement
Source
https://github.com/advisories/GHSA-2qq7-fch2-phqf
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/09/GHSA-2qq7-fch2-phqf/GHSA-2qq7-fch2-phqf.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-2qq7-fch2-phqf
Aliases
  • CVE-2024-47197
Published
2024-09-26T09:31:42Z
Modified
2024-10-02T21:23:00.152624Z
Severity
  • 3.1 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N CVSS Calculator
  • 2.1 (Low) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
Maven Archetype Plugin: Maven Archetype integration-test may package local settings into the published artifact, possibly containing credentials
Details

Exposure of Sensitive Information to an Unauthorized Actor, Insecure Storage of Sensitive Information vulnerability in Maven Archetype Plugin.

This issue affects Maven Archetype Plugin: from 3.2.1 before 3.3.0.

Users are recommended to upgrade to version 3.3.0, which fixes the issue.

Archetype integration testing creates a file called ./target/classes/archetype-it/archetype-settings.xml This file contains all the content from the users ~/.m2/settings.xml file, which often contains information they do not want to publish. We expect that on many developer machines, this also contains credentials.

When the user runs mvn verify again (without a mvn clean), this file becomes part of the final artifact.

If a developer were to publish this into Maven Central or any other remote repository (whether as a release or a snapshot) their credentials would be published without them knowing.

References

Affected packages

Maven / org.apache.maven.plugins:maven-archetype-plugin

Package

Name
org.apache.maven.plugins:maven-archetype-plugin
View open source insights on deps.dev
Purl
pkg:maven/org.apache.maven.plugins/maven-archetype-plugin

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.2.1
Fixed
3.3.0

Affected versions

3.*

3.2.1