CVE-2020-35573: High severity Postsrsd Project Postsrsd vulnerability

Published Dec 20, 2020
·
Updated

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.

Affected Software

18 affected componentsFixes available
Postsrsd Project Postsrsd<1.10
Debian Debian Linux=9.0
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
alpine/postsrsd<1.6-r4
1.6-r4
ubuntu/postsrsd<1.2-1ubuntu0.1~esm1
1.2-1ubuntu0.1~esm1
ubuntu/postsrsd<1.4-1ubuntu0.1
1.4-1ubuntu0.1
ubuntu/postsrsd<1.5-2ubuntu0.1~esm1
1.5-2ubuntu0.1~esm1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/postsrsd to a version that resolves this vulnerability.

    Fixed in 1.6-r4
  2. Upgrade

    Upgrade ubuntu/postsrsd to a version that resolves this vulnerability.

    Fixed in 1.2-1ubuntu0.1~esm1
  3. Upgrade

    Upgrade ubuntu/postsrsd to a version that resolves this vulnerability.

    Fixed in 1.4-1ubuntu0.1
  4. Upgrade

    Upgrade ubuntu/postsrsd to a version that resolves this vulnerability.

    Fixed in 1.5-2ubuntu0.1~esm1

Event History

Dec 20, 2020
CVE Published
via MITRE·04:53 AM
Data Sourced
via MITRE·04:53 AM
Description
Data Sourced
via OSV·05:15 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·05:15 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What access does an attacker need to trigger the denial of service?

The issue is remotely exploitable and requires no privileges or user interaction. An attacker can use an SRS address containing a long timestamp tag to cause CPU consumption.

2

Which versions are affected?

PostSRSd versions before 1.10 are affected.

3

What should teams do to remediate this issue?

Apply the available patch or update to a fixed PostSRSd version. The provided references include the upstream fix and distribution security advisories.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203