{"answers":{"affected":"3 open source packages ship an affected version, including restrictedpython and RestrictedPython. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-47532 in the wild and no public exploit code.","fix":"Upgrade restrictedpython to 7.3 or later.","what":"CVE-2024-47532 is a high-severity vulnerability in zopefoundation RestrictedPython, published on 30 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47532 and fix it if it is affected.\n\nWhat it is: CVE-2024-47532 is a high-severity vulnerability in zopefoundation RestrictedPython, published on 30 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47532 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- restrictedpython (PyPI): affected all versions; fixed in 7.3\n- restrictedpython (PyPI): affected all versions; fixed in 7.3\n- RestrictedPython (PyPI): affected all versions; fixed in 7.3\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-2024-47532/ (Markdown: https://insights.sbomify.com/CVE-2024-47532/index.md)","id":"CVE-2024-47532","markdown":"https://insights.sbomify.com/CVE-2024-47532/index.md","name":"CVE-2024-47532","record":{"aliases":["DEBIAN-CVE-2024-47532","GHSA-5rfv-66g4-jr8h","PYSEC-2024-186","UBUNTU-CVE-2024-47532"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python restricted execution library","requires_auth":"none","summary":"Attackers can access protected information in RestrictedPython via AttributeError.obj and the string module, exposing sensitive data in restricted environments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"restrictedpython","vendor":"zope"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"RestrictedPython is a restricted execution environment for Python to run untrusted code. A user can gain access to protected (and potentially sensible) information indirectly via AttributeError.obj and the string module. The problem will be fixed in version 7.3. As a workaround, If the application does not require access to the module string, it can remove it from RestrictedPython.Utilities.utility_builtins or otherwise do not make it available in the restricted execution environment.","ecosystems":["PyPI"],"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":"RestrictedPython information leakage via `AttributeError.obj` and the `string` module","id":"CVE-2024-47532","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Cobbler allows anyone to connect to cobbler XML-RPC server with a known password and make changes","id":"CVE-2024-47533"},"packages":[{"ecosystem":"PyPI","fixed":["7.3"],"introduced":["0"],"last_affected":[],"package":"RestrictedPython","purl":null,"source":"GHSA-5rfv-66g4-jr8h"},{"ecosystem":"PyPI","fixed":["7.3"],"introduced":["0"],"last_affected":[],"package":"restrictedpython","purl":"pkg:pypi/restrictedpython","source":"GHSA-5rfv-66g4-jr8h"},{"ecosystem":"PyPI","fixed":["7.3"],"introduced":["0"],"last_affected":[],"package":"restrictedpython","purl":"pkg:pypi/restrictedpython","source":"PYSEC-2024-186"}],"prev":{"headline":"Scout contains insufficient output escaping of attachment names","id":"CVE-2024-47531"},"products":["RestrictedPython"],"published":"2024-09-30","related":[{"cvss_score":8.4,"headline":"RestrictedPython vulnerable to arbitrary code execution via stack frame sandbox escape","id":"CVE-2023-37271","kev_date_added":null,"published":"2023-07-11"},{"cvss_score":8.3,"headline":"Sandbox escape via various forms of \"format\" in RestrictedPython","id":"CVE-2023-41039","kev_date_added":null,"published":"2023-08-30"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-30","vendors":["zopefoundation"]},"summary":"Attackers can access protected information in RestrictedPython via AttributeError.obj and the string module, exposing sensitive data in restricted environments.","url":"https://insights.sbomify.com/CVE-2024-47532/"}