CVE-2020-20658
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 · uneditedBuffer overflow vulnerability in fcovatti libiec_iccp_mod v1.5, allows attackers to cause a denail of service when trying to calloc an unexpectiedly large space.
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 confidenceBuffer overflow vulnerability in libiec_iccp_mod v1.5 where calloc is invoked with an unexpectedly large memory allocation size, causing a denial of service. The vulnerability stems from missing validation of user-controlled or calculated values before the memory allocation call.
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.5CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Confirm libiec_iccp_mod presenceSearch for the library file (libiec_iccp_mod.so, libiec_iccp_mod.dll, or libiec_iccp_mod.a) in your application directories, system libraries, or dependency manifests (package.json, requirements.txt, Cargo.lock, etc.)Affected if The library is present in your environment
-
Verify the exact versionCheck the version of libiec_iccp_mod by inspecting the library file metadata, version info embedded in the binary, or the dependency version specification in your project's build filesAffected if The version is exactly 1.5
-
Identify if ICCP protocol processing is activeInspect running processes or application logs for ICCP (Inter-Control Center Communications Protocol) server or client functionality that utilizes libiec_iccp_mod for IEC 60870-6 ICRC or TASE.2/SCADA communicationsAffected if The application actively processes ICCP protocol traffic using this library
-
Determine if untrusted ICCP data reaches the libraryReview network configuration or application architecture to determine whether ICCP messages from external or untrusted sources are processed by the libiec_iccp_mod component without prior sanitizationAffected if External or untrusted ICCP messages are processed by the vulnerable library
You are affected only if you use libiec_iccp_mod version 1.5 and your application processes external ICCP protocol data with this library, as the vulnerability triggers when unvalidated values are passed to calloc during message handling.
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 dataImplement rigorous input validation on all values used in memory allocation calculations to ensure they fall within reasonable bounds before calling calloc, preventing allocation of excessively large memory regions.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-20658 — 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-2020-20658 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