CVE-2010-0293
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe client logging functionality in chronyd in Chrony before 1.23.1 does not restrict the amount of memory used for storage of client information, which allows remote attackers to cause a denial of service (memory consumption) via spoofed (1) NTP or (2) cmdmon packets.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe chronyd daemon's client logging functionality in Chrony versions before 1.23.1 lacks memory allocation limits for storing client information. Remote attackers can send spoofed NTP or cmdmon packets to trigger unlimited memory consumption, resulting in denial of service via memory exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.23-pre1= 1.18= 1.19= 1.19-1= 1.19.99.1= 1.19.99.2= 1.19.99.3= 1.20= 1.21= 1.21-pre1= 1.24-pre1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrony versionRun `chronyd --version` or `rpm -q chrony` or `dpkg -l chrony` to identify the installed version numberAffected if The version is 1.23-pre1 or earlier, or matches any of these: 1.18, 1.19, 1.19-1, 1.19.99.1, 1.19.99.2, 1.19.99.3, 1.20, 1.21, 1.21-pre1, 1.24-pre1
-
Verify chronyd is runningRun `ps aux | grep chronyd` or `systemctl status chronyd` to confirm the daemon is activeAffected if chronyd is running on a vulnerable version
-
Confirm client logging or cmdmon is accessibleCheck chrony.conf for 'cmdport' or 'cmdallow' directives, or verify port 323 is listening with `netstat -ulnp | grep 323` or `ss -ulnp | grep 323`Affected if The cmdmon port 323 is open and accessible, enabling remote packet reception
-
Assess network exposureReview firewall rules or `iptables -L` to determine if NTP port 123 and cmdmon port 323 are exposed to untrusted networksAffected if Port 123 or 323 is reachable from external or untrusted networks without filtering
You are affected if chronyd is running a version before 1.23.1 with cmdmon or NTP ports exposed to the network, allowing remote attackers to send packets that trigger unbounded memory allocation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Chrony 1.23.1 or later which implements memory bounds checking. If immediate upgrade is not feasible, implement network-level rate limiting or firewall rules to restrict suspicious packet volumes.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-0293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data