# CVE-2007-3257: Integer overflow in n/a > A remote IMAP server can execute arbitrary code on Evolution Data Server clients by sending a negative SEQUENCE value, requiring user interaction to connect. - **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something - **Fix available:** Yes - **Published:** 19 Jun 2007 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2007-3257, DSA-1321-1, GHSA-6ggg-vv7h-7mm5, RHSA-2007:0509, RHSA-2007:0510 ## What is CVE-2007-3257? CVE-2007-3257 is a medium-severity vulnerability in n/a, published on 19 Jun 2007. 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 Camel (camel-imap-folder.c) in the mailer component for Evolution Data Server 1.11 allows remote IMAP servers to execute arbitrary code via a negative SEQUENCE value in GData, which is used as an array index. ## Which versions are affected by CVE-2007-3257? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `evolution` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-21.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-21.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-21.el3 | | `evolution` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-21.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-21.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-21.el3 | | `evolution` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-21.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-21.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-21.el3 | | `evolution` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-21.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-21.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-21.el3 | | `evolution` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4 | | `evolution` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4 | | `evolution` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4 | | `evolution` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4 | | `evolution-data-server` | Red Hat:enterprise_linux:5::client | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server` | Red Hat:enterprise_linux:5::server | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.8.0-15.0.4.el5 | | `evolution-data-server-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.8.0-15.0.4.el5 | Products: Gnome Evolution. ## How do I fix CVE-2007-3257? Apply the vendor's patch. ## Is CVE-2007-3257 being exploited? There is no known exploitation of CVE-2007-3257 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-2008-1108](https://insights.sbomify.com/CVE-2008-1108/): Memory corruption in n/a (high 7.6) - [CVE-2013-4166](https://insights.sbomify.com/CVE-2013-4166/): Information disclosure in Evolution (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2007-3257 and fix it if it is affected. What it is: CVE-2007-3257 is a medium-severity vulnerability in n/a, published on 19 Jun 2007. 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-2007-3257 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-2007-3257/ (Markdown: https://insights.sbomify.com/CVE-2007-3257/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2007-3257 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-3257 - OSV: https://osv.dev/vulnerability/CVE-2007-3257 --- From sbomify Insights: https://insights.sbomify.com/CVE-2007-3257/ Summaries are generated and may contain mistakes; the official description above is the record.