CVE-2021-3570: Buffer Overflow

Published May 31, 2021
·
Updated

A flaw was found in the ptp4l program of the linuxptp package. A missing length check when forwarding a PTP message between ports allows a remote attacker to cause an information leak, crash, or potentially remote code execution. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. This flaw affects linuxptp versions before 3.1.1, before 2.0.1, before 1.9.3, before 1.8.1, before 1.7.1, before 1.6.1 and before 1.5.1.

Other sources

When ptp4l is forwarding a PTP message between ports, it uses the messageLength field as the length of transmitted data, but it does not check if the value is not larger than the actual length of the received message. An attacker with access to the network can send a crafted message to cause ptp4l to send data past the message buffer, causing an information leak or crash. If ptp4l runs on a little-endian architecture, the attacker can also craft a management message which causes a heap memory corruption by converting fields from host to network order, potentially leading to remote code execution.

Red Hat

Affected Software

27 affected componentsFixes available
debian/linuxptp
1.9.2-1+deb10u13.1-2.13.1.1-44.0-1
debian/linuxptp<=3.1-2, <=1.9.2-1
3.1-2.11.9.2-1+deb10u1
redhat/linuxptp<3.1.1
3.1.1
redhat/linuxptp<2.0.1
2.0.1
redhat/linuxptp<1.9.3
1.9.3
redhat/linuxptp<1.8.1
1.8.1
redhat/linuxptp<1.7.1
1.7.1
redhat/linuxptp<1.6.1
1.6.1
redhat/linuxptp<1.5.1
1.5.1
Linuxptp Project Linuxptp<1.5.1
Linuxptp Project Linuxptp>=1.6.0<1.6.1
Linuxptp Project Linuxptp>=1.8.0<1.8.1
Linuxptp Project Linuxptp>=1.9.0<1.9.3
Linuxptp Project Linuxptp>=2.0.0<2.0.1
Linuxptp Project Linuxptp>=3.0.0<3.1.1
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux Aus=8.2
redhat Enterprise Linux Aus=8.4
redhat Enterprise Linux Eus=8.1
redhat Enterprise Linux Eus=8.2
redhat Enterprise Linux Tus=8.2
redhat Enterprise Linux Tus=8.4
Fedoraproject Fedora=33
Fedoraproject Fedora=34
Debian Debian Linux=10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linuxptp to a version that resolves this vulnerability.

    Fixed in 1.9.2-1+deb10u1Fixed in 3.1-2.1Fixed in 3.1.1-4Fixed in 4.0-1
  2. Upgrade

    Upgrade debian/linuxptp to a version that resolves this vulnerability.

    Fixed in 3.1-2.1Fixed in 1.9.2-1+deb10u1
  3. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 3.1.1
  4. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 2.0.1
  5. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 1.9.3
  6. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 1.8.1
  7. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 1.7.1
  8. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 1.6.1
  9. Upgrade

    Upgrade redhat/linuxptp to a version that resolves this vulnerability.

    Fixed in 1.5.1
  10. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 3.1.1
  11. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 2.0.1
  12. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 1.9.3
  13. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 1.8.1
  14. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 1.7.1
  15. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 1.6.1
  16. Upgrade

    Upgrade linuxptp/ptp4l (ptp4l) to a version that resolves this vulnerability.

    Fixed in 1.5.1
  17. Compensating control

    Limit network access to ptp4l (send only trusted PTP traffic to the hosts running ptp4l), since an attacker with network access can send crafted PTP messages to trigger the missing length check and potential heap corruption.

Event History

Jul 9, 2021
CVE Published
via MITRE·10:33 AM
Data Sourced
via MITRE·10:33 AM
DescriptionWeakness
Data Sourced
via NVD·11: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-2021-3570?

The severity of CVE-2021-3570 is high (8.8).

2

How does CVE-2021-3570 impact data confidentiality?

CVE-2021-3570 can potentially lead to data confidentiality breaches.

3

What is the affected software for CVE-2021-3570?

The affected software for CVE-2021-3570 includes Linuxptp Project Linuxptp, Redhat Enterprise Linux, and Fedora.

4

How can I fix CVE-2021-3570?

To fix CVE-2021-3570, it is recommended to update the linuxptp package to version 1.9.2-1+deb10u1 (for Debian) or 3.1-2.1 (for other distributions).

5

Where can I find more information about CVE-2021-3570?

You can find more information about CVE-2021-3570 at the following references: [reference 1](https://security-tracker.debian.org/tracker/CVE-2021-3570), [reference 2](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3570), [reference 3](https://security-tracker.debian.org/tracker/CVE-2021-3571).

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