CVE-2009-0547: Evolution 2.22.3.1 checks S/MIME signatures against a copy of the e-mail text within a signed-data blob, not t

Routine

MEDIUM 5.0DOWNGRADE

CVE-2009-0547 is a medium-severity flaw (CVSS 5.0) affecting evolution. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Evolution 2.22.3.1 checks S/MIME signatures against a copy of the e-mail text within a signed-data blob, not the copy of the e-mail text displayed to the user, which allows remote attackers to spoof a signature by modifying the latter copy, a different vulnerability than CVE-2008-5077.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	2.2% (top 17%)
CISA exploited list	No
Weakness	CWE-310
Published	2009-02-12
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: evolution

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2009-02-12 23:30 UTCPublished CVE record published
2026-06-16 23:05 UTCUpdated Record last modified

evolution evolution DOWNGRADE

Affected: 2.22.3.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.22.3.1

1. Check installed version

apt-cache policy evolution || rpm -q evolution || evolution --version

2. No fixed release: DOWNGRADE to a release before 2.22.3.1 (Debian / Ubuntu)

apt-cache madison evolution sudo apt install evolution=<VERSION_BEFORE_2.22.3.1> sudo apt-mark hold evolution

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list evolution sudo dnf downgrade evolution-<VERSION_BEFORE_2.22.3.1> sudo dnf versionlock add evolution

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2009-0547?

evolution: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2009-0547 being exploited?

CVE-2009-0547 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2009-0547 affect?

CVE-2009-0547 affects evolution. Severity is medium (CVSS 5.0). Evolution 2.22.3.1 checks S/MIME signatures against a copy of the e-mail text within a signed-data blob, not the copy of the e-mail text displayed to the user, which allows remote attackers to spoof a signature by modifying the latter copy,

How urgent is CVE-2009-0547?

Priority 38/100. No elevated risk signals yet.

Related CVEs

CVE-2024-29844 CRITICAL 9.8 UPGRADE Default credentials on the Web Interface of Evolution Controller 2.x allows anyone to log in to the server dir
CVE-2024-29843 HIGH 7.5 UPGRADE The Web interface of Evolution Controller Versions 2.04.560.31.03.2024 and below contains poorly configured ac
CVE-2024-29842 HIGH 7.5 UPGRADE The Web interface of Evolution Controller Versions 2.04.560.31.03.2024 and below contains poorly configured ac
CVE-2024-29841 HIGH 7.5 UPGRADE The Web interface of Evolution Controller Versions 2.04.560.31.03.2024 and below contains poorly configured ac
CVE-2024-29840 HIGH 7.5 UPGRADE The Web interface of Evolution Controller Versions 2.04.560.31.03.2024 and below contains poorly configured ac

References

← Back to latest CVEs