{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.plugins:github-coverage-reporter. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-2212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-2212 is a medium-severity vulnerability in Jenkins GitHub Coverage Reporter Plugin, published on 2 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-2212 and fix it if it is affected.\n\nWhat it is: CVE-2020-2212 is a medium-severity vulnerability in Jenkins GitHub Coverage Reporter Plugin, published on 2 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-2212 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.plugins:github-coverage-reporter (Maven): affected all versions up to 1.10; no fix listed\n- io.jenkins.plugins:github-coverage-reporter (Maven): affected all versions up to 1.10; 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-2020-2212/ (Markdown: https://insights.sbomify.com/CVE-2020-2212/index.md)","id":"CVE-2020-2212","markdown":"https://insights.sbomify.com/CVE-2020-2212/index.md","name":"CVE-2020-2212","record":{"aliases":["GHSA-5r5f-hcwf-r9jh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with file system or configuration read access can view unencrypted secrets stored by the Jenkins GitHub Coverage Reporter Plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"github_coverage_reporter","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Jenkins GitHub Coverage Reporter Plugin 1.8 and earlier stores secrets unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system or read permissions on the system configuration.","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":"Secret stored in plain text by Jenkins GitHub Coverage Reporter Plugin","id":"CVE-2020-2212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Credentials stored in plain text by Jenkins White Source Plugin","id":"CVE-2020-2213"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.10"],"package":"io.jenkins.plugins:github-coverage-reporter","purl":null,"source":"GHSA-5r5f-hcwf-r9jh"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.10"],"package":"io.jenkins.plugins:github-coverage-reporter","purl":"pkg:maven/io.jenkins.plugins/github-coverage-reporter","source":"GHSA-5r5f-hcwf-r9jh"}],"prev":{"headline":"RCE vulnerability in ElasticBox Jenkins Kubernetes CI/CD Plugin","id":"CVE-2020-2211"},"products":["Jenkins GitHub Coverage Reporter Plugin"],"published":"2020-07-02","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 file system or configuration read access can view unencrypted secrets stored by the Jenkins GitHub Coverage Reporter Plugin.","url":"https://insights.sbomify.com/CVE-2020-2212/"}