{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:database. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2242 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:database to 1.7 or later.","what":"CVE-2020-2242 is a medium-severity missing authorization vulnerability in Jenkins database Plugin, published on 1 Sep 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-2242 and fix it if it is affected.\n\nWhat it is: CVE-2020-2242 is a medium-severity missing authorization vulnerability in Jenkins database Plugin, published on 1 Sep 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-2242 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:database (Maven): affected all versions; fixed in 1.7\n- org.jenkins-ci.plugins:database (Maven): affected all versions; fixed in 1.7\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-2242/ (Markdown: https://insights.sbomify.com/CVE-2020-2242/index.md)","id":"CVE-2020-2242","markdown":"https://insights.sbomify.com/CVE-2020-2242/index.md","name":"CVE-2020-2242","record":{"aliases":["GHSA-hj36-v72x-cc6j"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins database Plugin","requires_auth":"low_privilege","summary":"Attackers with read access can connect to arbitrary databases using their own credentials due to missing permission checks in the Jenkins database plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"database","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A missing permission check in Jenkins database Plugin 1.6 and earlier allows attackers with Overall/Read access to Jenkins to connect to an attacker-specified database server using attacker-specified credentials.","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":"Missing permission checks in Jenkins Database Plugin","id":"CVE-2020-2242","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Stored XSS vulnerability in Jenkins Cadence vManager Plugin","id":"CVE-2020-2243"},"packages":[{"ecosystem":"Maven","fixed":["1.7"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:database","purl":null,"source":"GHSA-hj36-v72x-cc6j"},{"ecosystem":"Maven","fixed":["1.7"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:database","purl":"pkg:maven/org.jenkins-ci.plugins/database","source":"GHSA-hj36-v72x-cc6j"}],"prev":{"headline":"CSRF vulnerability in Jenkins Database Plugin","id":"CVE-2020-2241"},"products":["Jenkins database Plugin"],"published":"2020-09-01","related":[{"cvss_score":8.8,"headline":"CSRF vulnerability in Jenkins Database Plugin","id":"CVE-2020-2240","kev_date_added":null,"published":"2020-09-01"},{"cvss_score":8.8,"headline":"CSRF vulnerability in Jenkins Database Plugin","id":"CVE-2020-2241","kev_date_added":null,"published":"2020-09-01"}],"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 read access can connect to arbitrary databases using their own credentials due to missing permission checks in the Jenkins database plugin.","url":"https://insights.sbomify.com/CVE-2020-2242/"}