Improper Certificate Validation Affecting syslog-ng package, versions <3.38.1-5+deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-SYSLOGNG-18067280
- published21 Jul 2026
- disclosed7 May 2025
Introduced: 7 May 2025
CVE-2024-47619 (opens in a new tab)How to fix?
Upgrade Echo:latest syslog-ng to version 3.38.1-5+deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream syslog-ng package and not the syslog-ng package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
syslog-ng is an enhanced log daemo. Prior to version 4.8.2, tls_wildcard_match() matches on certificates such as foo.*.bar although that is not allowed. It is also possible to pass partial wildcards such as foo.a*c.bar which glib matches but should be avoided / invalidated. This issue could have an impact on TLS connections, such as in man-in-the-middle situations. Version 4.8.2 contains a fix for the issue.
References
- https://www.cve.org/CVERecord?id=CVE-2024-47619
- https://github.com/syslog-ng/syslog-ng/blob/b0ccc8952d333fbc2d97e51fddc0b569a15e7a7d/lib/transport/tls-verifier.c#L78-L110
- https://github.com/syslog-ng/syslog-ng/commit/dadfdbecde5bfe710b0a6ee5699f96926b3f9006
- https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-4.8.2
- https://lists.debian.org/debian-lts-announce/2025/05/msg00034.html
- https://github.com/syslog-ng/syslog-ng/security/advisories/GHSA-xr54-gx74-fghg