CVE-2020-35573 json
srs2.c in PostSRSd before 1.10 allows remote attackers to cause a denial of service (CPU consumption) via a long timestamp tag in an SRS ad…
published 5y ago modified 4mo ago also EUVD-2020-23239
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
srs2.c in PostSRSd before 1.10 allows remote attackers to cause a denial of service (CPU consumption) via a long timestamp tag in an SRS address.
Patch / fix
- postsrsd_project postsrsd 1.10
- postsrsd Debian 14, Debian 13, Debian 12 1.10-1
debian advisories DEBIAN-CVE-2020-35573
- postsrsd Ubuntu 18.04 LTS 1.4-1ubuntu0.1
ubuntu advisories UBUNTU-CVE-2020-35573
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- postsrsd openSUSE Tumbleweed 1.11-1.3
- postsrsd Package Hub 15 SP3, openSUSE Leap 15.3 1.11-bp153.2.3.1
- postsrsd Package Hub 15 SP2 1.11-bp152.4.3.1
- postsrsd openSUSE Leap 15.2 1.11-lp152.4.3.1
opensuse advisories openSUSE-SU-2024:11188-1openSUSE-SU-2021:1642-1openSUSE-SU-2021:0669-1openSUSE-SU-2021:0646-1
- postsrsd Alpine 3.24, Alpine 3.23, Alpine 3.22 +10 more 1.6-r4
alpine advisories ALPINE-CVE-2020-35573
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2020-35573 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-35573 updated cvss 7.5
postsrsd: specially crafted SRS address could lead to DoS
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.69% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-834 Excessive Iteration
References
-
github.com
/roehling/postsrsd/commit/4733fb11f6bec6524bb8518c5e1a699288c26bac
patch, third-party-advisory
-
security.gentoo.org
/glsa/202107-08
vendor-advisory, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2020/12/msg00031.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2020-35573
- NVD CVE-2020-35573
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.