{"answers":{"affected":"2 open source packages ship an affected version, including jenkins.xtc:extensivetesting. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10448 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10448 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10448 is a high-severity vulnerability in Jenkins Extensive Testing Plugin, published on 16 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10448 and fix it if it is affected.\n\nWhat it is: CVE-2019-10448 is a high-severity vulnerability in Jenkins Extensive Testing Plugin, published on 16 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10448 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jenkins.xtc:extensivetesting (Maven): affected all versions; no fix listed\n- jenkins.xtc:extensivetesting (Maven): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-10448/ (Markdown: https://insights.sbomify.com/CVE-2019-10448/index.md)","id":"CVE-2019-10448","markdown":"https://insights.sbomify.com/CVE-2019-10448/index.md","name":"CVE-2019-10448","record":{"aliases":["GHSA-8x6c-375h-pm4f"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with Extended Read permission or master file system access can view unencrypted credentials stored in Jenkins Extensive Testing Plugin job configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"extensive_testing","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Extensive Testing Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cleartext Storage of Sensitive Information in Jenkins Extensive Testing Plugin","id":"CVE-2019-10448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Fortify on Demand Plugin stores credentials in plain text","id":"CVE-2019-10449"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":[],"last_affected":[],"package":"jenkins.xtc:extensivetesting","purl":null,"source":"GHSA-8x6c-375h-pm4f"},{"ecosystem":"Maven","fixed":[],"introduced":[],"last_affected":[],"package":"jenkins.xtc:extensivetesting","purl":"pkg:maven/jenkins.xtc/extensivetesting","source":"GHSA-8x6c-375h-pm4f"}],"prev":{"headline":"Jenkins Sofy.AI Plugin stores API token in plain text","id":"CVE-2019-10447"},"products":["Jenkins Extensive Testing Plugin"],"published":"2019-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Jenkins project"]},"summary":"Attackers with Extended Read permission or master file system access can view unencrypted credentials stored in Jenkins Extensive Testing Plugin job configurations.","url":"https://insights.sbomify.com/CVE-2019-10448/"}