# CVE-2005-2491: Integer overflow in n/a > Attackers can execute arbitrary code via heap-based buffer overflow caused by integer overflow in PCRE regular expression compilation. - **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:** 22 Aug 2005 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2005-2491, DSA-800-1, DSA-817-1, DSA-819-1, DSA-821-1, DTSA-10-1, GHSA-h9j2-347v-3v58, RHSA-2005:358, RHSA-2005:761, RHSA-2006:0197 ## What is CVE-2005-2491? CVE-2005-2491 is a high-severity vulnerability in n/a, published on 22 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Integer overflow in pcre_compile.c in Perl Compatible Regular Expressions (PCRE) before 6.2, as used in multiple products such as Python, Ethereal, and PHP, allows attackers to execute arbitrary code via quantifier values in regular expressions, which leads to a heap-based buffer overflow. ## Which versions are affected by CVE-2005-2491? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pcre` | Red Hat:enterprise_linux:3::as | All versions | 0:3.9-10.2 | | `pcre-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:3.9-10.2 | | `pcre-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:3.9-10.2 | | `python` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.2 | | `python-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.2 | | `python-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.2 | | `python-tools` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.2 | | `tkinter` | Red Hat:enterprise_linux:3::as | All versions | 0:2.2.3-6.2 | | `pcre` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.9-10.2 | | `pcre-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.9-10.2 | | `pcre-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.9-10.2 | | `python` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.2 | | `python-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.2 | | `python-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.2 | | `python-tools` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.2 | | `tkinter` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.2.3-6.2 | | `pcre` | Red Hat:enterprise_linux:3::es | All versions | 0:3.9-10.2 | | `pcre-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:3.9-10.2 | | `pcre-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:3.9-10.2 | | `python` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.2 | | `python-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.2 | | `python-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.2 | | `python-tools` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.2 | | `tkinter` | Red Hat:enterprise_linux:3::es | All versions | 0:2.2.3-6.2 | | `pcre` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.9-10.2 | | `pcre-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.9-10.2 | | `pcre-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.9-10.2 | | `python` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.2 | | `python-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.2 | | `python-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.2 | | `python-tools` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.2 | | `tkinter` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.2.3-6.2 | | `exim` | Red Hat:enterprise_linux:4::as | All versions | 0:4.43-1.RHEL4.5 | | `exim-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:4.43-1.RHEL4.5 | | `exim-doc` | Red Hat:enterprise_linux:4::as | All versions | 0:4.43-1.RHEL4.5 | | `exim-mon` | Red Hat:enterprise_linux:4::as | All versions | 0:4.43-1.RHEL4.5 | | `exim-sa` | Red Hat:enterprise_linux:4::as | All versions | 0:4.43-1.RHEL4.5 | | `pcre` | Red Hat:enterprise_linux:4::as | All versions | 0:4.5-3.2.RHEL4 | | `pcre-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:4.5-3.2.RHEL4 | | `pcre-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:4.5-3.2.RHEL4 | Products: Pcre Pcre. ## How do I fix CVE-2005-2491? Upgrade to a fixed version. ## Is CVE-2005-2491 being exploited? There is no known exploitation of CVE-2005-2491 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2015-3210](https://insights.sbomify.com/CVE-2015-3210/): Memory corruption in n/a (critical 9.8) - [CVE-2016-3191](https://insights.sbomify.com/CVE-2016-3191/): Memory corruption in n/a (critical 9.8) - [CVE-2017-7245](https://insights.sbomify.com/CVE-2017-7245/): Memory corruption in n/a (high 7.8) - [CVE-2017-7246](https://insights.sbomify.com/CVE-2017-7246/): Memory corruption in n/a (high 7.8) - [CVE-2017-11164](https://insights.sbomify.com/CVE-2017-11164/): Denial of service in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2005-2491 and fix it if it is affected. What it is: CVE-2005-2491 is a high-severity vulnerability in n/a, published on 22 Aug 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-2491 in the wild and no public exploit code. Affected product: n/a. 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-2491/ (Markdown: https://insights.sbomify.com/CVE-2005-2491/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2005-2491 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-2491 - OSV: https://osv.dev/vulnerability/CVE-2005-2491 --- From sbomify Insights: https://insights.sbomify.com/CVE-2005-2491/ Summaries are generated and may contain mistakes; the official description above is the record.