# CVE-2008-1108: Memory corruption in n/a > Remote attackers can execute arbitrary code via a crafted iCalendar attachment if the ITip Formatter plugin is disabled. - **Severity:** High 7.6 (`AV:N/AC:H/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:** 4 Jun 2008 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2008-1108, GHSA-839c-2pvm-jv7q, RHSA-2008:0516, RHSA-2008:0517 ## What is CVE-2008-1108? CVE-2008-1108 is a high-severity memory corruption vulnerability in n/a, published on 4 Jun 2008. 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 Buffer overflow in Evolution 2.22.1, when the ITip Formatter plugin is disabled, allows remote attackers to execute arbitrary code via a long timezone string in an iCalendar attachment. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2008-1108? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `evolution` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-22.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-22.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-22.el3 | | `evolution` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-22.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-22.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-22.el3 | | `evolution` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-22.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-22.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-22.el3 | | `evolution` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-22.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-22.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-22.el3 | | `evolution` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4_6.2 | | `evolution` | Red Hat:rhel_eus:4.5::as | All versions | 0:2.0.2-35.0.4.el4_5.2 | | `evolution-debuginfo` | Red Hat:rhel_eus:4.5::as | All versions | 0:2.0.2-35.0.4.el4_5.2 | | `evolution-devel` | Red Hat:rhel_eus:4.5::as | All versions | 0:2.0.2-35.0.4.el4_5.2 | | `evolution` | Red Hat:rhel_eus:4.5::es | All versions | 0:2.0.2-35.0.4.el4_5.2 | | `evolution-debuginfo` | Red Hat:rhel_eus:4.5::es | All versions | 0:2.0.2-35.0.4.el4_5.2 | | `evolution-devel` | Red Hat:rhel_eus:4.5::es | All versions | 0:2.0.2-35.0.4.el4_5.2 | Products: Gnome Evolution. ## How do I fix CVE-2008-1108? Apply the vendor's patch. ## Is CVE-2008-1108 being exploited? There is no known exploitation of CVE-2008-1108 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2018-12422](https://insights.sbomify.com/CVE-2018-12422/): Memory corruption in n/a (critical 9.8) - [CVE-2008-1109](https://insights.sbomify.com/CVE-2008-1109/): Memory corruption in n/a (critical 9.3) - [CVE-2009-3721](https://insights.sbomify.com/CVE-2009-3721/): Path traversal in ytnef (high 7.8) - [CVE-2013-4166](https://insights.sbomify.com/CVE-2013-4166/): Information disclosure in Evolution (high 7.5) - [CVE-2005-2549](https://insights.sbomify.com/CVE-2005-2549/): Memory corruption in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2008-1108 and fix it if it is affected. What it is: CVE-2008-1108 is a high-severity memory corruption vulnerability in n/a, published on 4 Jun 2008. 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-2008-1108 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-2008-1108/ (Markdown: https://insights.sbomify.com/CVE-2008-1108/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2008-1108 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-1108 - OSV: https://osv.dev/vulnerability/CVE-2008-1108 --- From sbomify Insights: https://insights.sbomify.com/CVE-2008-1108/ Summaries are generated and may contain mistakes; the official description above is the record.