CVE-2012-4502
What it is
Multiple integer overflows in pktlength.c in Chrony before 1.29 allow remote attackers to cause a denial of service (crash) via a crafted (1) REQ_SUBNETS_ACCESSED or (2) REQ_CLIENT_ACCESSES command request to the PKL_CommandLength function or crafted (3) RPY_SUBNETS_ACCESSED, (4) RPY_CLIENT_ACCESSES, (5) RPY_CLIENT_ACCESSES_BY_INDEX, or (6) RPY_MANUAL_LIST command reply to the PKL_ReplyLength function, which triggers an out-of-bounds read or buffer overflow. NOTE: versions 1.27 and 1.28 do not require authentication to exploit.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 3.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.2% in the next 30 days (EPSS).
- Severity: 5.0 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.2% · EPSS, next 30 days
- Weakness
- CWE-189
- Record status
- Modified
Affected
- Tuxfamily Chrony ≤ 1.28
- Tuxfamily Chrony 1.0
- Tuxfamily Chrony 1.1
- Tuxfamily Chrony 1.18
- Tuxfamily Chrony 1.19
- Tuxfamily Chrony 1.19.99.1
- Tuxfamily Chrony 1.19.99.2
- Tuxfamily Chrony 1.19.99.3
Attack profile CVSS 2.0 · 5.0
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2012-4502.md and follow it. Check whether this project is affected by CVE-2012-4502. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://permalink.gmane.org/gmane.comp.time.chrony.announce/15
- http://seclists.org/oss-sec/2013/q3/332
- https://bugzilla.redhat.com/show_bug.cgi?id=846392
- http://permalink.gmane.org/gmane.comp.time.chrony.announce/15
- http://seclists.org/oss-sec/2013/q3/332
- https://bugzilla.redhat.com/show_bug.cgi?id=846392
References
- http://git.tuxfamily.org/chrony/chrony.git/?p=chrony/chrony.git%3Ba=commitdiff%3Bh=7712455d9aa33d0db0945effaa07e900b85987b1
- http://permalink.gmane.org/gmane.comp.time.chrony.announce/15
- http://seclists.org/oss-sec/2013/q3/332
- http://www.debian.org/security/2013/dsa-2760
- https://bugzilla.redhat.com/show_bug.cgi?id=846392
- http://git.tuxfamily.org/chrony/chrony.git/?p=chrony/chrony.git%3Ba=commitdiff%3Bh=7712455d9aa33d0db0945effaa07e900b85987b1
- http://permalink.gmane.org/gmane.comp.time.chrony.announce/15
- http://seclists.org/oss-sec/2013/q3/332
- http://www.debian.org/security/2013/dsa-2760
- https://bugzilla.redhat.com/show_bug.cgi?id=846392