# CVE-2006-4514: Memory corruption in n/a > Heap-based buffer overflow in libgsf allows arbitrary code execution via a malicious OLE document, requiring user interaction to open the file. - **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:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 Nov 2006 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2006-4514, DSA-1221-1, GHSA-rp23-2xcw-7j87, RHSA-2007:0011 ## What is CVE-2006-4514? CVE-2006-4514 is a high-severity memory corruption vulnerability in n/a, published on 30 Nov 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Heap-based buffer overflow in the ole_info_read_metabat function in Gnome Structured File library (libgsf) 1.14.0, and other versions before 1.14.2, allows context-dependent attackers to execute arbitrary code via a large num_metabat value in an OLE document, which causes the ole_init_info function to allocate insufficient memory. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2006-4514? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libgsf` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.0-7 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.0-7 | | `libgsf-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.0-7 | | `libgsf` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.0-7 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.0-7 | | `libgsf-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.0-7 | | `libgsf` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.0-7 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.0-7 | | `libgsf-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.0-7 | | `libgsf` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.0-7 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.0-7 | | `libgsf-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.0-7 | | `libgsf` | Red Hat:enterprise_linux:4::as | All versions | 0:1.10.1-2 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.10.1-2 | | `libgsf-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.10.1-2 | | `libgsf` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.10.1-2 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.10.1-2 | | `libgsf-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.10.1-2 | | `libgsf` | Red Hat:enterprise_linux:4::es | All versions | 0:1.10.1-2 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.10.1-2 | | `libgsf-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.10.1-2 | | `libgsf` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.10.1-2 | | `libgsf-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.10.1-2 | | `libgsf-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.10.1-2 | Products: Libgsf Libgsf. ## How do I fix CVE-2006-4514? Upgrade to a fixed version. ## Is CVE-2006-4514 being exploited? There is no known exploitation of CVE-2006-4514 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2006-4514 and fix it if it is affected. What it is: CVE-2006-4514 is a high-severity memory corruption vulnerability in n/a, published on 30 Nov 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2006-4514 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-2006-4514/ (Markdown: https://insights.sbomify.com/CVE-2006-4514/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2006-4514 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-4514 - OSV: https://osv.dev/vulnerability/CVE-2006-4514 --- From sbomify Insights: https://insights.sbomify.com/CVE-2006-4514/ Summaries are generated and may contain mistakes; the official description above is the record.