CVE-2010-4336
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 cu_rrd_create_file function (src/utils_rrdcreate.c) in collectd 4.x before 4.9.4 and before 4.10.2 allow remote attackers to cause a denial of service (assertion failure) via a packet with a timestamp whose value is 10 or less, as demonstrated by creating RRD files using the (1) RRDtool and (2) RRDCacheD plugins.
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 · moderate confidenceThe cu_rrd_create_file function in collectd versions 4.x before 4.9.4 and 4.10.2 contains an assertion that fails when processing RRD creation packets with timestamps of 10 or less, causing a denial of service. The vulnerability affects both the RRDtool and RRDCacheD plugins and can be exploited remotely by sending specially crafted packets with invalid timestamps.
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= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 4.0.8= 4.0.9= 4.1.0= 4.1.1CVSS 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.
-
Identify collectd versionRun 'collectd -v' or check the package version (dpkg -l collectd, rpm -q collectd)Affected if Version is 4.x before 4.9.4 or before 4.10.2 (e.g., 4.0.0 through 4.1.1 and other 4.x versions below the fixed releases)
-
Check if RRDtool plugin is enabledInspect collectd.conf for 'LoadPlugin rrdtool' and verify the plugin is not commented outAffected if RRDtool plugin is loaded and active
-
Check if RRDCacheD plugin is enabledInspect collectd.conf for 'LoadPlugin rrdcache' or 'LoadPlugin rrdcached' and verify the plugin is not commented outAffected if RRDCacheD plugin is loaded and active
-
Verify network listening statusCheck if collectd binds to network ports (look for 'Listen' directives in collectd.conf or run 'netstat -anp | grep collectd')Affected if Collectd is listening on network interfaces, allowing remote packet delivery
You are affected if you run a vulnerable collectd 4.x version (before 4.9.4 or 4.10.2) AND have either the RRDtool or RRDCacheD plugin enabled with network exposure.
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 collectd 4.9.4 or 4.10.2 or later, which contain the fix for proper timestamp validation before RRD file creation. Alternatively, restrict network access to collectd's RRD creation interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4336 — 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-4336 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