Bug 1966241 (CVE-2021-3571)
Summary: | CVE-2021-3571 linuxptp: wrong length of one-step follow-up in transparent clock | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Guilherme de Almeida Suckevicz <gsuckevi> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | mcascell, mlichvar, security-response-team, yalli |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | linuxptp 3.1.1, linuxptp 2.0.1 | Doc Type: | If docs needed, set a value |
Doc Text: |
A flaw was found in the ptp4l program of the linuxptp package. When ptp4l is operating on a little-endian architecture as a PTP transparent clock, a remote attacker could send a crafted one-step sync message to cause an information leak or crash. The highest threat from this vulnerability is to data confidentiality and system availability.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-11-09 19:23:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1966509, 1966517, 1979401 | ||
Bug Blocks: | 1966236, 1966242 |
Description
Guilherme de Almeida Suckevicz
2021-05-31 17:31:39 UTC
Upstream fix: https://sourceforge.net/p/linuxptp/code/ci/d61d77e163dbee247819f3d88593ba111577af15 [master] https://sourceforge.net/p/linuxptp/code/ci/0b3ab45de6a96ca181a5cf62c3c2b97167e2ed20 [v3.1.1] https://sourceforge.net/p/linuxptp/code/ci/2eac9118ca82c2d368df5490f4be96ee9e32a80c [v2.0.1] Created linuxptp tracking bugs for this issue: Affects: fedora-all [bug 1979401] This flaw has been rated as having a Moderate impact. The information leak is probably not very useful on its own as ptp4l doesn't handle any sensitive or confidential data like passwords, private keys, etc. This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2021:4321 https://access.redhat.com/errata/RHSA-2021:4321 This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2021-3571 |