# CVE-2007-1558: Weak cryptography in n/a > Remote attackers can guess password prefixes via MITM attacks exploiting MD5 collisions in APOP, affecting email clients like Thunderbird and Evolution. - **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`) - **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:** 16 Apr 2007 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2007-1558, GHSA-jmh6-7c53-fg26, RHSA-2007:0344, RHSA-2007:0353, RHSA-2007:0385, openSUSE-SU-2024:11615-1 ## What is CVE-2007-1558? CVE-2007-1558 is a low-severity vulnerability in n/a, published on 16 Apr 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 The APOP protocol allows remote attackers to guess the first 3 characters of a password via man-in-the-middle (MITM) attacks that use crafted message IDs and MD5 collisions. NOTE: this design-level issue potentially affects all products that use APOP, including (1) Thunderbird 1.x before 1.5.0.12 and 2.x before 2.0.0.4, (2) Evolution, (3) mutt, (4) fetchmail before 6.3.8, (5) SeaMonkey 1.0.x before 1.0.9 and 1.1.x before 1.1.2, (6) Balsa 2.3.16 and earlier, (7) Mailfilter before 0.8.2, and possibly other products. ## Which versions are affected by CVE-2007-1558? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `fetchmail` | Red Hat:enterprise_linux:2.1::as | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmailconf` | Red Hat:enterprise_linux:2.1::as | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmail` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmailconf` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmail` | Red Hat:enterprise_linux:2.1::es | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmailconf` | Red Hat:enterprise_linux:2.1::es | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmail` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `fetchmailconf` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:5.9.0-21.7.3.el2.1.6 | | `evolution` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-20.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-20.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-20.el3 | | `fetchmail` | Red Hat:enterprise_linux:3::as | All versions | 0:6.2.0-3.el3.4 | | `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:6.2.0-3.el3.4 | | `evolution` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-20.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-20.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-20.el3 | | `fetchmail` | Red Hat:enterprise_linux:3::desktop | All versions | 0:6.2.0-3.el3.4 | | `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:6.2.0-3.el3.4 | | `evolution` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-20.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-20.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-20.el3 | | `fetchmail` | Red Hat:enterprise_linux:3::es | All versions | 0:6.2.0-3.el3.4 | | `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:6.2.0-3.el3.4 | | `evolution` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-20.el3 | | `evolution-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-20.el3 | | `evolution-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-20.el3 | | `fetchmail` | Red Hat:enterprise_linux:3::ws | All versions | 0:6.2.0-3.el3.4 | | `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:6.2.0-3.el3.4 | | `evolution` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.2.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.2.el4 | | `evolution-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.2.el4 | | `fetchmail` | Red Hat:enterprise_linux:4::as | All versions | 0:6.2.5-6.0.1.el4 | | `fetchmail-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:6.2.5-6.0.1.el4 | | `evolution` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.2.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.2.el4 | | `evolution-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.2.el4 | | `fetchmail` | Red Hat:enterprise_linux:4::desktop | All versions | 0:6.2.5-6.0.1.el4 | | `fetchmail-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:6.2.5-6.0.1.el4 | | `evolution` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.2.el4 | | `evolution-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.2.el4 | Products: Apop Protocol Apop Protocol. ## How do I fix CVE-2007-1558? Upgrade to a fixed version. ## Is CVE-2007-1558 being exploited? There is no known exploitation of CVE-2007-1558 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2007-1558 and fix it if it is affected. What it is: CVE-2007-1558 is a low-severity vulnerability in n/a, published on 16 Apr 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-1558 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-1558/ (Markdown: https://insights.sbomify.com/CVE-2007-1558/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2007-1558 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-1558 - OSV: https://osv.dev/vulnerability/CVE-2007-1558 --- From sbomify Insights: https://insights.sbomify.com/CVE-2007-1558/ Summaries are generated and may contain mistakes; the official description above is the record.