{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:email-ext. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-32979 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:email-ext to 2.96.1 or later.","what":"CVE-2023-32979 is a medium-severity vulnerability in Jenkins Email Extension Plugin, published on 16 May 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-32979 and fix it if it is affected.\n\nWhat it is: CVE-2023-32979 is a medium-severity vulnerability in Jenkins Email Extension Plugin, published on 16 May 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-32979 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:email-ext (Maven): affected all versions; fixed in 2.96.1\n- org.jenkins-ci.plugins:email-ext (Maven): affected all versions; fixed in 2.96.1\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-32979/ (Markdown: https://insights.sbomify.com/CVE-2023-32979/index.md)","id":"CVE-2023-32979","markdown":"https://insights.sbomify.com/CVE-2023-32979/index.md","name":"CVE-2023-32979","record":{"aliases":["GHSA-6gp4-2f92-j2w5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Email Extension Plugin","requires_auth":"low_privilege","summary":"Attackers with read permissions can verify file existence in the Jenkins home directory due to missing permission checks in form validation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"email_extension","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","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-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Jenkins Email Extension Plugin does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read permission to check for the existence of files in the email-templates/ directory in the Jenkins home directory on the controller 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":"Jenkins Email Extension Plugin missing permission check","id":"CVE-2023-32979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Email Extension Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2023-32980"},"packages":[{"ecosystem":"Maven","fixed":["2.96.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:email-ext","purl":null,"source":"GHSA-6gp4-2f92-j2w5"},{"ecosystem":"Maven","fixed":["2.96.1"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:email-ext","purl":"pkg:maven/org.jenkins-ci.plugins/email-ext","source":"GHSA-6gp4-2f92-j2w5"}],"prev":{"headline":"Jenkins LDAP Plugin vulnerable to Cross-Site Request Forgery","id":"CVE-2023-32978"},"products":["Jenkins Email Extension Plugin"],"published":"2023-05-16","related":[{"cvss_score":9.9,"headline":"Sandbox escape in Jenkins Email Extension Plugin","id":"CVE-2023-25765","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":9.9,"headline":"Script security sandbox bypass in Jenkins Email Extension Plugin","id":"CVE-2019-1003032","kev_date_added":null,"published":"2019-03-08"},{"cvss_score":8.8,"headline":"Jenkins Email Extension Plugin: Attackers able to control email content may specify `file:` URLs for images to read arbitrary files from Jenkins controller filesystem","id":"CVE-2026-48920","kev_date_added":null,"published":"2026-05-27"},{"cvss_score":7.5,"headline":"Jenkins Email Extension Plugin SMTP password transmitted and displayed in plain text","id":"CVE-2020-2232","kev_date_added":null,"published":"2020-08-12"},{"cvss_score":6.5,"headline":"Jenkins Email Extension Plugin showed plain text SMTP password in configuration form field","id":"CVE-2018-1000176","kev_date_added":null,"published":"2018-05-08"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins Email Extension Plugin","id":"CVE-2023-25763","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins Email Extension Plugin","id":"CVE-2023-25764","kev_date_added":null,"published":"2023-02-15"}],"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":"2025-01-23","vendors":["Jenkins Project"]},"summary":"Attackers with read permissions can verify file existence in the Jenkins home directory due to missing permission checks in form validation.","url":"https://insights.sbomify.com/CVE-2023-32979/"}