{"answers":{"affected":"2 open source packages ship an affected version, including net.arangamani.jenkins:gem-publisher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10426 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10426 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10426 is a medium-severity vulnerability in Jenkins Gem Publisher Plugin, published on 25 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10426 and fix it if it is affected.\n\nWhat it is: CVE-2019-10426 is a medium-severity vulnerability in Jenkins Gem Publisher Plugin, published on 25 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10426 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.arangamani.jenkins:gem-publisher (Maven): affected all versions up to 1.0; no fix listed\n- net.arangamani.jenkins:gem-publisher (Maven): affected all versions up to 1.0; 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-10426/ (Markdown: https://insights.sbomify.com/CVE-2019-10426/index.md)","id":"CVE-2019-10426","markdown":"https://insights.sbomify.com/CVE-2019-10426/index.md","name":"CVE-2019-10426","record":{"aliases":["GHSA-6pqm-pp65-mc26"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jenkins Gem Publisher Plugin","requires_auth":"low_privilege","summary":"Attackers with master file system access can read unencrypted credentials stored by the Jenkins Gem Publisher Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"gem_publisher","vendor":"jenkins"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins Gem Publisher Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with 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":"Jenkins Gem Publisher Plugin stores credentials as plaintext","id":"CVE-2019-10426","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Aqua MicroScanner Plugin showed plain text credential in configuration form","id":"CVE-2019-10427"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.0"],"package":"net.arangamani.jenkins:gem-publisher","purl":null,"source":"GHSA-6pqm-pp65-mc26"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.0"],"package":"net.arangamani.jenkins:gem-publisher","purl":"pkg:maven/net.arangamani.jenkins/gem-publisher","source":"GHSA-6pqm-pp65-mc26"}],"prev":{"headline":"Jenkins Google Calendar Plugin has Insufficiently Protected Credentials","id":"CVE-2019-10425"},"products":["Jenkins Gem Publisher Plugin"],"published":"2019-09-25","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 master file system access can read unencrypted credentials stored by the Jenkins Gem Publisher Plugin.","url":"https://insights.sbomify.com/CVE-2019-10426/"}