CVE-2019-16791: downgrade of effective Strict Transport Security (STS) policy in postfix-mta-sts-resolver

Published Jul 5, 2019
·
Updated

Incorrect query parsing

Impact All users of versions prior to 0.5.1 can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.

Patches Problem has been patched in version 0.5.1

Workarounds Users may remediate this vulnerability without upgrading by applying these patches to older suppoorted versions.

For more information If you have any questions or comments about this advisory: Open an issue in postfix-mta-sts-resolver repo Email me at vladislav at vm-0 dot com

Other sources

In postfix-mta-sts-resolver before 0.5.1, All users can receive incorrect response from daemon under rare conditions, rendering downgrade of effective STS policy.

Affected Software

2 affected componentsFixes available
pip/postfix-mta-sts-resolver<0.5.1
0.5.1
Postfix-mta-sts-resolver Project Postfix-mta-sts-resolver<0.5.1

Event History

Jul 5, 2019
Advisory Published
via GitHub·09:06 PM
Jan 22, 2020
CVE Published
via MITRE·01:40 AM
Data Sourced
via MITRE·01:40 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2019-16791?

CVE-2019-16791 is considered a medium severity vulnerability due to the potential impact on the effective STS policy.

2

How do I fix CVE-2019-16791?

To fix CVE-2019-16791, upgrade to version 0.5.1 of postfix-mta-sts-resolver or a later version.

3

Who is affected by CVE-2019-16791?

CVE-2019-16791 affects all users of postfix-mta-sts-resolver versions prior to 0.5.1.

4

What impact does CVE-2019-16791 have?

CVE-2019-16791 can cause users to receive incorrect responses from the daemon, potentially leading to a downgrade of the effective STS policy.

5

Is there a workaround for CVE-2019-16791?

No specific workaround is suggested for CVE-2019-16791 other than upgrading to the patched version.

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