# CVE-2005-0089: Code injection in n/a > Remote attackers can execute arbitrary code or modify data in Python XML-RPC servers using register_instance without _dispatch. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Feb 2005 - **Updated:** 7 Aug 2024 - **Also known as:** AZL-109545, DSA-666-1, GHSA-w2rh-7p2w-889c, RHSA-2005:108, RHSA-2005:109 ## What is CVE-2005-0089? CVE-2005-0089 is a high-severity code injection vulnerability in Python Python, published on 6 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The SimpleXMLRPCServer library module in Python 2.2, 2.3 before 2.3.5, and 2.4, when used by XML-RPC servers that use the register_instance method to register an object without a _dispatch method, allows remote attackers to read or modify globals of the associated module, and possibly execute arbitrary code, via dotted attributes. ## Which versions are affected by CVE-2005-0089? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `python` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.1 | | `python-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.1 | | `python-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.1 | | `python-tools` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.1 | | `tkinter` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.1 | | `python` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.1 | | `python-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.1 | | `python-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.1 | | `python-tools` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.1 | | `tkinter` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.1 | | `python` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.1 | | `python-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.1 | | `python-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.1 | | `python-tools` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.1 | | `tkinter` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.1 | | `python` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.1 | | `python-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.1 | | `python-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.1 | | `python-tools` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.1 | | `tkinter` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.1 | | `python` | Red Hat:enterprise_linux:4::as | All versions | 0:2.3.4-14.1 | | `python-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.3.4-14.1 | | `python-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.3.4-14.1 | | `python-docs` | Red Hat:enterprise_linux:4::as | All versions | 0:2.3.4-14.1 | | `python-tools` | Red Hat:enterprise_linux:4::as | All versions | 0:2.3.4-14.1 | | `tkinter` | Red Hat:enterprise_linux:4::as | All versions | 0:2.3.4-14.1 | | `python` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.3.4-14.1 | | `python-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.3.4-14.1 | | `python-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.3.4-14.1 | | `python-docs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.3.4-14.1 | | `python-tools` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.3.4-14.1 | | `tkinter` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.3.4-14.1 | | `python` | Red Hat:enterprise_linux:4::es | All versions | 0:2.3.4-14.1 | | `python-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.3.4-14.1 | | `python-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.3.4-14.1 | | `python-docs` | Red Hat:enterprise_linux:4::es | All versions | 0:2.3.4-14.1 | | `python-tools` | Red Hat:enterprise_linux:4::es | All versions | 0:2.3.4-14.1 | | `tkinter` | Red Hat:enterprise_linux:4::es | All versions | 0:2.3.4-14.1 | | `python` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.3.4-14.1 | | `python-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.3.4-14.1 | Products: Python Python. ## How do I fix CVE-2005-0089? Upgrade to a fixed version. ## Is CVE-2005-0089 being exploited? There is no known exploitation of CVE-2005-0089 in the wild and no public exploit code. ## Other vulnerabilities in Python Python - [CVE-2008-5031](https://insights.sbomify.com/CVE-2008-5031/): Integer overflow in n/a (critical 10.0) - [CVE-2014-4650](https://insights.sbomify.com/CVE-2014-4650/): Path traversal in n/a (critical 9.8) - [CVE-2016-5636](https://insights.sbomify.com/CVE-2016-5636/): Integer overflow in n/a (critical 9.8) - [CVE-2007-4559](https://insights.sbomify.com/CVE-2007-4559/): Path traversal in n/a (critical 9.8) - [CVE-2017-17522](https://insights.sbomify.com/CVE-2017-17522/): Command injection in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2005-0089 and fix it if it is affected. What it is: CVE-2005-0089 is a high-severity code injection vulnerability in Python Python, published on 6 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2005-0089 in the wild and no public exploit code. Affected product: Python Python. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2005-0089/ (Markdown: https://insights.sbomify.com/CVE-2005-0089/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2005-0089 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-0089 - OSV: https://osv.dev/vulnerability/CVE-2005-0089 --- From sbomify Insights: https://insights.sbomify.com/CVE-2005-0089/ Summaries are generated and may contain mistakes; the official description above is the record.