# CVE-2010-4267: Memory corruption in n/a > Remote attackers can cause a crash or execute arbitrary code via a crafted SNMP response in HPLIP due to a stack-based buffer overflow. - **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:** 20 Jan 2011 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2010-4267, DSA-2152-1, GHSA-9c9p-hhrq-f5v5, RHSA-2011:0154 ## What is CVE-2010-4267? CVE-2010-4267 is a high-severity memory corruption vulnerability in n/a, published on 20 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Stack-based buffer overflow in the hpmud_get_pml function in io/hpmud/pml.c in Hewlett-Packard Linux Imaging and Printing (HPLIP) 1.6.7, 3.9.8, 3.10.9, and probably other versions allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted SNMP response with a large length value. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2010-4267? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `hpijs` | Red Hat:enterprise_linux:5::server | All versions | 1:1.6.7-6.el5_6.1 | | `hpijs3` | Red Hat:enterprise_linux:5::server | All versions | 1:3.9.8-11.el5_6.1 | | `hplip` | Red Hat:enterprise_linux:5::server | All versions | 0:1.6.7-6.el5_6.1 | | `hplip-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.6.7-6.el5_6.1 | | `hplip3` | Red Hat:enterprise_linux:5::server | All versions | 0:3.9.8-11.el5_6.1 | | `hplip3-common` | Red Hat:enterprise_linux:5::server | All versions | 0:3.9.8-11.el5_6.1 | | `hplip3-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:3.9.8-11.el5_6.1 | | `hplip3-gui` | Red Hat:enterprise_linux:5::server | All versions | 0:3.9.8-11.el5_6.1 | | `hplip3-libs` | Red Hat:enterprise_linux:5::server | All versions | 0:3.9.8-11.el5_6.1 | | `libsane-hpaio` | Red Hat:enterprise_linux:5::server | All versions | 0:1.6.7-6.el5_6.1 | | `libsane-hpaio3` | Red Hat:enterprise_linux:5::server | All versions | 0:3.9.8-11.el5_6.1 | | `hpijs` | Red Hat:enterprise_linux:6::client | All versions | 1:3.9.8-33.el6_0.1 | | `hplip` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-common` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-gui` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.8-33.el6_0.1 | | `libsane-hpaio` | Red Hat:enterprise_linux:6::client | All versions | 0:3.9.8-33.el6_0.1 | | `hpijs` | Red Hat:enterprise_linux:6::server | All versions | 1:3.9.8-33.el6_0.1 | | `hplip` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-common` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-gui` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.8-33.el6_0.1 | | `libsane-hpaio` | Red Hat:enterprise_linux:6::server | All versions | 0:3.9.8-33.el6_0.1 | | `hpijs` | Red Hat:enterprise_linux:6::workstation | All versions | 1:3.9.8-33.el6_0.1 | | `hplip` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-common` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-gui` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.8-33.el6_0.1 | | `hplip-libs` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.8-33.el6_0.1 | | `libsane-hpaio` | Red Hat:enterprise_linux:6::workstation | All versions | 0:3.9.8-33.el6_0.1 | Products: Hp Linux Imaging and Printing Project. ## How do I fix CVE-2010-4267? Apply the vendor's patch. ## Is CVE-2010-4267 being exploited? There is no known exploitation of CVE-2010-4267 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2007-5208](https://insights.sbomify.com/CVE-2007-5208/): Command injection in n/a (high 7.6) - [CVE-2008-2940](https://insights.sbomify.com/CVE-2008-2940/): Privilege escalation in n/a (high 7.2) - [CVE-2013-4325](https://insights.sbomify.com/CVE-2013-4325/): Race condition in n/a (medium 6.9) - [CVE-2013-6427](https://insights.sbomify.com/CVE-2013-6427/): Code injection in n/a (medium 6.8) - [CVE-2011-2697](https://insights.sbomify.com/CVE-2011-2697/): Command injection in n/a (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2010-4267 and fix it if it is affected. What it is: CVE-2010-4267 is a high-severity memory corruption vulnerability in n/a, published on 20 Jan 2011. 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-2010-4267 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-2010-4267/ (Markdown: https://insights.sbomify.com/CVE-2010-4267/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2010-4267 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-4267 - OSV: https://osv.dev/vulnerability/CVE-2010-4267 --- From sbomify Insights: https://insights.sbomify.com/CVE-2010-4267/ Summaries are generated and may contain mistakes; the official description above is the record.