Every CVE Search/ Get API key

MGASA-2013-0296

Updated ssmtp package fixes security vulnerability

No scoreFix available

It was reported that ssmtp, an extremely simple MTA to get mail off the system to a mail hub, did not perform x509 certificate validation when initiating a TLS connection to server. A rogue server could use this flaw to conduct man-in- the-middle attack, possibly leading to user credentials leak.

As a result, alterations may be required to the configuration if using TLS. The default ssmtp.conf now contains the lines below to load root certificates which should be created as ssmtp.conf.rpmnew if it has been altered.

#IMPORTANT: Uncomment the following line if you use TLS authentication #TLS_CA_File=/etc/pki/tls/certs/ca-bundle.crt

What each source reports

OSV No score

Updated ssmtp package fixes security vulnerability

It was reported that ssmtp, an extremely simple MTA to get mail off the system to a mail hub, did not perform x509 certificate validation when initiating a TLS connection to server. A rogue server could use this flaw to conduct man-in- the-middle attack, possibly leading to user credentials leak.

As a result, alterations may be required to the configuration if using TLS. The default ssmtp.conf now contains the lines below to load root certificates which should be created as ssmtp.conf.rpmnew if it has been altered.

#IMPORTANT: Uncomment the following line if you use TLS authentication #TLS_CA_File=/etc/pki/tls/certs/ca-bundle.crt

Record
MGASA-2013-0296
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
ssmtp
Mageia:2
before 2.64-5.3.mga2
2.64-5.3.mga2
ssmtp
Mageia:3
before 2.64-8.3.mga3
2.64-8.3.mga3

History

History
RecordedChangedSources
first indexedOSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

MGASA-2013-0296 is a vulnerability with no CVSS score yet in ssmtp, published October 9, 2013. No source lists public exploit code. Fixed in ssmtp 2.64-5.3.mga2.

References

MoveEnter Open