{"answers":{"affected":"2 open source packages ship an affected version, including org.datadog.jenkins.plugins:datadog. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000114 in the wild and no public exploit code.","fix":"Upgrade org.datadog.jenkins.plugins:datadog to 0.6.2 or later.","what":"CVE-2017-1000114 is a low-severity vulnerability in n/a, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-1000114 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000114 is a low-severity vulnerability in n/a, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-1000114 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.datadog.jenkins.plugins:datadog (Maven): affected all versions; fixed in 0.6.2\n- org.datadog.jenkins.plugins:datadog (Maven): affected all versions; fixed in 0.6.2\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-2017-1000114/ (Markdown: https://insights.sbomify.com/CVE-2017-1000114/index.md)","id":"CVE-2017-1000114","markdown":"https://insights.sbomify.com/CVE-2017-1000114/index.md","name":"CVE-2017-1000114","record":{"aliases":["GHSA-hf7w-f4h4-9xp8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Datadog plugin","requires_auth":"none","summary":"Attackers can steal Datadog API keys transmitted in plaintext during Jenkins configuration, potentially compromising monitoring services.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"datadog","vendor":"jenkins"}],"cvss":{"score":3.1,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Datadog Plugin stores an API key to access the Datadog service in the global Jenkins configuration. While the API key is stored encrypted on disk, it was transmitted in plain text as part of the configuration form. This could result in exposure of the API key for example through browser extensions or cross-site scripting vulnerabilities. The Datadog Plugin now encrypts the API key transmitted to administrators viewing the global configuration form.","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":"Exposure of Sensitive Information in Jenkins Datadog plugin","id":"CVE-2017-1000114","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Mercurial missing symlink check","id":"CVE-2017-1000115"},"packages":[{"ecosystem":"Maven","fixed":["0.6.2"],"introduced":["0"],"last_affected":[],"package":"org.datadog.jenkins.plugins:datadog","purl":null,"source":"GHSA-hf7w-f4h4-9xp8"},{"ecosystem":"Maven","fixed":["0.6.2"],"introduced":["0"],"last_affected":[],"package":"org.datadog.jenkins.plugins:datadog","purl":"pkg:maven/org.datadog.jenkins.plugins/datadog","source":"GHSA-hf7w-f4h4-9xp8"}],"prev":{"headline":"Jenkins Deploy to container Plugin stored plain text passwords in job configuration","id":"CVE-2017-1000113"},"products":["n/a"],"published":"2017-10-04","related":[{"cvss_score":6.5,"headline":"Jenkins Datadog Plugin does not perform a permission check in an HTTP endpoint.","id":"CVE-2023-37944","kev_date_added":null,"published":"2023-07-12"}],"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-05","vendors":["n/a"]},"summary":"Attackers can steal Datadog API keys transmitted in plaintext during Jenkins configuration, potentially compromising monitoring services.","url":"https://insights.sbomify.com/CVE-2017-1000114/"}