Shared MemoApplication · Evolution

CVE-2007-1002

MEDIUM · 6.8 CVSS v2.0 Published 2007-03-21

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

77/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Format string vulnerability in the write_html function in calendar/gui/e-cal-component-memo-preview.c in Evolution Shared Memo 2.8.2.1, and possibly earlier versions, allows user-assisted remote attackers to execute arbitrary code via format specifiers in the categories of a crafted shared memo.

Technical summary

dbcve analysis · high confidence

Format string vulnerability in Evolution Shared Memo (calender/gui/e-cal-component-memo-preview.c) allows arbitrary code execution via format specifiers embedded in the categories field of a crafted shared memo. The write_html function passes user-controlled input directly to a format string function without proper sanitization.

MitigationUpdate Evolution to a version newer than 2.8.2.1 that contains the patched code, or apply the fix that properly formats the user input (e.g., using %s specifier) before passing it to the format string function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Shared MemoApplication

Affected:= 2.8.2.1

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Evolution is installed

Run 'evolution --version' or check for the evolution package using your system's package manager (e.g., dpkg -l | grep evolution, rpm -qa | grep evolution)

Affected if Evolution is not installed or not present on the system
Determine the installed Evolution version

Execute 'evolution --version' to obtain the exact version number, or use your package manager to query the installed evolution package version

Affected if The version is exactly 2.8.2.1
Confirm the vulnerable component exists

Check for the presence of the file e-cal-component-memo-preview.c in the Evolution source or check the installed files using package manager (e.g., dpkg -L evolution | grep memo-preview)

Affected if The vulnerable file exists in the installation
Check if Shared Memo functionality is accessible

Attempt to access the Shared Memo feature in Evolution (usually via Calendar > Memos) or verify the evolution-memo package is installed

Affected if Shared Memo feature is available and user can create or view memos

If Evolution version is exactly 2.8.2.1 and the Shared Memo feature is accessible, the environment is affected by CVE-2007-1002.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update Evolution to a version newer than 2.8.2.1 that contains the patched code, or apply the fix that properly formats the user input (e.g., using %s specifier) before passing it to the format string function.

Fix this in Shared Memo Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing3.0 h
Review / QA2.0 h

10.0 hours of engineering $1,750

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2007-1002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1002 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2007-1002?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 6.8 Medium

Exploit likelihood EPSS, next 30 days 3.4%

Affects: Shared Memo

Remediation

A high-priority fix

Fix this in Shared Memo 10 hrs · Moderate

Typical engagement from $1,750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2007-1002 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References