{"answers":{"affected":"2 open source packages ship an affected version, including io.jenkins.plugins:frugal-testing. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41947 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41947 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41947 is a medium-severity missing authorization vulnerability in Jenkins Frugal Testing Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41947 and fix it if it is affected.\n\nWhat it is: CVE-2023-41947 is a medium-severity missing authorization vulnerability in Jenkins Frugal Testing Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-41947 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.jenkins.plugins:frugal-testing (Maven): affected all versions up to 1.1; no fix listed\n- io.jenkins.plugins:frugal-testing (Maven): affected all versions up to 1.1; 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-2023-41947/ (Markdown: https://insights.sbomify.com/CVE-2023-41947/index.md)","id":"CVE-2023-41947","markdown":"https://insights.sbomify.com/CVE-2023-41947/index.md","name":"CVE-2023-41947","record":{"aliases":["GHSA-p986-hpr3-493p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with read access can connect to Frugal Testing using arbitrary credentials due to missing permission checks in the Jenkins plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"frugal_testing","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-862","name":"Missing Authorization"}],"description":"A missing permission check in Jenkins Frugal Testing Plugin 1.1 and earlier allows attackers with Overall/Read permission to connect to Frugal Testing 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":false,"headline":"Missing permission checks in Jenkins Frugal Testing Plugin","id":"CVE-2023-41947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"WordPress Cookie Notice \u0026 Consent Plugin \u003c= 1.6.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-41948"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.1"],"package":"io.jenkins.plugins:frugal-testing","purl":null,"source":"GHSA-p986-hpr3-493p"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.1"],"package":"io.jenkins.plugins:frugal-testing","purl":"pkg:maven/io.jenkins.plugins/frugal-testing","source":"GHSA-p986-hpr3-493p"}],"prev":{"headline":"CSRF vulnerability in Jenkins Frugal Testing Plugin","id":"CVE-2023-41946"},"products":["Jenkins Frugal Testing Plugin"],"published":"2023-09-06","related":[{"cvss_score":3.5,"headline":"CSRF vulnerability in Jenkins Frugal Testing Plugin","id":"CVE-2023-41946","kev_date_added":null,"published":"2023-09-06"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["Jenkins Project"]},"summary":"Attackers with read access can connect to Frugal Testing using arbitrary credentials due to missing permission checks in the Jenkins plugin.","url":"https://insights.sbomify.com/CVE-2023-41947/"}