# Maven Archetype Plugin: Maven Archetype integration-test may package local settings into the published artifact, possibly containing credentials

Advisory record · `GHSA-2qq7-fch2-phqf`

- **Identifiers:** `GHSA-2qq7-fch2-phqf` · `CVE-2024-47197`
- **State:** Confirmed
- **Severity:** CVSS 3.1 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-922](https://cwe.mitre.org/data/definitions/922.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 26 Sept 2024
- **Updated:** 17 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Sept 2024, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.maven.plugins:maven-archetype-plugin` (Maven): affected `>=3.2.1, <3.3.0`; fixed in `3.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The maven-archetype-plugin versions from 3.2.1 before 3.3.0 can package a copy of the user's \~/.m2/settings.xml into the build output. When a developer runs mvn verify again without a clean, that file can end up in the published artifact and expose credentials stored in the settings file. Upgrade to maven-archetype-plugin 3.3.0, which fixes the issue.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.1 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0084, the 58th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2qq7-fch2-phqf)

## Sources

- [GitHub Advisory Database: GHSA-2qq7-fch2-phqf](https://github.com/advisories/GHSA-2qq7-fch2-phqf)
- [OSV: GHSA-2qq7-fch2-phqf](https://osv.dev/vulnerability/GHSA-2qq7-fch2-phqf)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-47197>
- <https://github.com/apache/maven-archetype/pull/188>
- <https://github.com/apache/maven-archetype/commit/484b6ab946f0d7ce557a3df28615d8c51e500054>
- <https://github.com/apache/maven-archetype>
- <https://issues.apache.org/jira/browse/ARCHETYPE-657>
- <https://lists.apache.org/thread/ftg81np183wnyk0kg4ks95dvgxdrof96>
- <http://www.openwall.com/lists/oss-security/2024/09/26/2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2qq7-fch2-phqf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2qq7-fch2-phqf/>. Everything for agents: <https://agentprime.io/llms.txt>.