# CVE-2009-3379: Memory corruption in n/a > Remote attackers can cause application crashes or execute arbitrary code via unspecified vectors in the libvorbis library used by Firefox. - **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 29 Oct 2009 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2009-3379, GHSA-f7fv-7rmr-mpcf, RHSA-2009:1561 ## What is CVE-2009-3379? CVE-2009-3379 is a critical memory corruption vulnerability in Mozilla Firefox, published on 29 Oct 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Multiple unspecified vulnerabilities in libvorbis, as used in Mozilla Firefox 3.5.x before 3.5.4, allow remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via unknown vectors. NOTE: this might overlap CVE-2009-2663. ## Which versions are affected by CVE-2009-3379? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libvorbis` | Red Hat:enterprise_linux:3::as | All versions | 1:1.0-12.el3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:1.0-12.el3 | | `libvorbis-devel` | Red Hat:enterprise_linux:3::as | All versions | 1:1.0-12.el3 | | `libvorbis` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.0-12.el3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.0-12.el3 | | `libvorbis-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.0-12.el3 | | `libvorbis` | Red Hat:enterprise_linux:3::es | All versions | 1:1.0-12.el3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:1.0-12.el3 | | `libvorbis-devel` | Red Hat:enterprise_linux:3::es | All versions | 1:1.0-12.el3 | | `libvorbis` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.0-12.el3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.0-12.el3 | | `libvorbis-devel` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.0-12.el3 | | `libvorbis` | Red Hat:enterprise_linux:4::as | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-devel` | Red Hat:enterprise_linux:4::as | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis` | Red Hat:enterprise_linux:4::desktop | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis` | Red Hat:enterprise_linux:4::es | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-devel` | Red Hat:enterprise_linux:4::es | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis` | Red Hat:enterprise_linux:4::ws | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis-devel` | Red Hat:enterprise_linux:4::ws | All versions | 1:1.1.0-3.el4_8.3 | | `libvorbis` | Red Hat:enterprise_linux:5::client | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis` | Red Hat:enterprise_linux:5::client_workstation | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis` | Red Hat:enterprise_linux:5::server | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 1:1.1.2-3.el5_4.4 | | `libvorbis-devel` | Red Hat:enterprise_linux:5::server | All versions | 1:1.1.2-3.el5_4.4 | Products: Mozilla Firefox. ## How do I fix CVE-2009-3379? Upgrade to a fixed version. ## Is CVE-2009-3379 being exploited? There is no known exploitation of CVE-2009-3379 in the wild and no public exploit code. ## Other vulnerabilities in Mozilla Firefox - [CVE-2019-11708](https://insights.sbomify.com/CVE-2019-11708/): Mozilla Firefox and Thunderbird Sandbox Escape (critical 10.0, exploited in the wild) - [CVE-2010-3765](https://insights.sbomify.com/CVE-2010-3765/): Mozilla Multiple Products Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2022-26486](https://insights.sbomify.com/CVE-2022-26486/): Mozilla Firefox Use-After-Free (critical 9.6, exploited in the wild) - [CVE-2022-26485](https://insights.sbomify.com/CVE-2022-26485/): Mozilla Firefox Use-After-Free (high 8.8, exploited in the wild) - [CVE-2019-11707](https://insights.sbomify.com/CVE-2019-11707/): Mozilla Firefox and Thunderbird Type Confusion (high 8.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2009-3379 and fix it if it is affected. What it is: CVE-2009-3379 is a critical memory corruption vulnerability in Mozilla Firefox, published on 29 Oct 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2009-3379 in the wild and no public exploit code. Affected product: Mozilla Firefox. 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-2009-3379/ (Markdown: https://insights.sbomify.com/CVE-2009-3379/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-3379 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-3379 - OSV: https://osv.dev/vulnerability/CVE-2009-3379 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-3379/ Summaries are generated and may contain mistakes; the official description above is the record.