{"uuid": "03b9a86d-3cbb-474b-bc21-c7d4c945fef1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47197", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7810", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-47197\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Exposure of Sensitive Information to an Unauthorized Actor, Insecure Storage of Sensitive Information vulnerability in Maven Archetype Plugin.\n\nThis issue affects Maven Archetype Plugin: from 3.2.1 before 3.3.0.\n\nUsers are recommended to upgrade to version 3.3.0, which fixes the issue.\n\nArchetype integration testing creates a file\ncalled ./target/classes/archetype-it/archetype-settings.xml\nThis file contains all the content from the users ~/.m2/settings.xml file,\nwhich often contains information they do not want to publish. We expect that on many developer machines, this also contains\ncredentials.\n\nWhen the user runs mvn verify again (without a mvn clean), this file becomes part of\nthe final artifact.\n\nIf a developer were to publish this into Maven Central or any other remote repository (whether as a release\nor a snapshot) their credentials would be published without them knowing.\n\ud83d\udccf Published: 2024-09-26T08:01:24.486Z\n\ud83d\udccf Modified: 2025-03-17T17:36:10.410Z\n\ud83d\udd17 References:\n1. https://lists.apache.org/thread/ftg81np183wnyk0kg4ks95dvgxdrof96", "creation_timestamp": "2025-03-17T18:31:35.000000Z"}