{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:gitlab-logo. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10429 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:gitlab-logo to 1.0.4 or later.","what":"CVE-2019-10429 is a medium-severity vulnerability in Jenkins GitLab Logo 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-10429 and fix it if it is affected.\n\nWhat it is: CVE-2019-10429 is a medium-severity vulnerability in Jenkins GitLab Logo 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-10429 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:gitlab-logo (Maven): affected all versions; fixed in 1.0.4\n- org.jenkins-ci.plugins:gitlab-logo (Maven): affected all versions; fixed in 1.0.4\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-10429/ (Markdown: https://insights.sbomify.com/CVE-2019-10429/index.md)","id":"CVE-2019-10429","markdown":"https://insights.sbomify.com/CVE-2019-10429/index.md","name":"CVE-2019-10429","record":{"aliases":["GHSA-22rj-q66g-2jg3"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jenkins GitLab Logo Plugin","requires_auth":"low_privilege","summary":"Attackers with master file system access can read unencrypted credentials stored by the Jenkins GitLab Logo Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"gitlab_logo","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 GitLab Logo 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":true,"headline":"Jenkins GitLab Logo Plugin stores credentials unencrypted","id":"CVE-2019-10429","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 NeuVector Vulnerability Scanner Plugin stored credentials in plain text","id":"CVE-2019-10430"},"packages":[{"ecosystem":"Maven","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-logo","purl":null,"source":"GHSA-22rj-q66g-2jg3"},{"ecosystem":"Maven","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-logo","purl":"pkg:maven/org.jenkins-ci.plugins/gitlab-logo","source":"GHSA-22rj-q66g-2jg3"}],"prev":{"headline":"Jenkins Aqua Security Scanner Plugin showed plain text password in configuration form","id":"CVE-2019-10428"},"products":["Jenkins GitLab Logo 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 GitLab Logo Plugin.","url":"https://insights.sbomify.com/CVE-2019-10429/"}