{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:influxdb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10329 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:influxdb to 1.22 or later.","what":"CVE-2019-10329 is a high-severity vulnerability in Jenkins InfluxDB Plugin, published on 31 May 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-10329 and fix it if it is affected.\n\nWhat it is: CVE-2019-10329 is a high-severity vulnerability in Jenkins InfluxDB Plugin, published on 31 May 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-10329 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:influxdb (Maven): affected all versions; fixed in 1.22\n- org.jenkins-ci.plugins:influxdb (Maven): affected all versions; fixed in 1.22\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-10329/ (Markdown: https://insights.sbomify.com/CVE-2019-10329/index.md)","id":"CVE-2019-10329","markdown":"https://insights.sbomify.com/CVE-2019-10329/index.md","name":"CVE-2019-10329","record":{"aliases":["GHSA-rv97-r8f7-8wmg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins InfluxDB Plugin","requires_auth":"low_privilege","summary":"Attackers with master file system access can read unencrypted credentials stored by the Jenkins InfluxDB Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"influxdb","vendor":"eficode"}],"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 InfluxDB Plugin 1.21 and earlier stored 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":"Plaintext password storage in Jenkins InfluxDB Plugin","id":"CVE-2019-10329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Improper handling of untrusted branches in Gitea Jenkins Plugin","id":"CVE-2019-10330"},"packages":[{"ecosystem":"Maven","fixed":["1.22"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:influxdb","purl":null,"source":"GHSA-rv97-r8f7-8wmg"},{"ecosystem":"Maven","fixed":["1.22"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:influxdb","purl":"pkg:maven/org.jenkins-ci.plugins/influxdb","source":"GHSA-rv97-r8f7-8wmg"}],"prev":{"headline":"Unsafe entry in Script Security list of approved signatures in Pipeline Remote Loader Plugin","id":"CVE-2019-10328"},"products":["Jenkins InfluxDB Plugin"],"published":"2019-05-31","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 InfluxDB Plugin.","url":"https://insights.sbomify.com/CVE-2019-10329/"}