Security readout for executives and security teams
Plain-English summary
CVE-2020-20335 is a denial-of-service flaw in Antirez Kilo. A buffer overflow in the row-update logic can let a remote attacker crash availability. The source bundle names no packaged product, CPE, release version, or active exploitation evidence.
Executive priority
Prioritize if Kilo-derived code is reachable over a network or embedded in operational tooling. Business impact is availability loss, not data theft, based on the provided CVSS and description.
Technical view
The CVE describes a buffer overflow in `editorUpdateRow` in `kilo.c` before commit `7709a04ae8520c5b04d261616098cebf742f5a23`. CVSS 3.1 is 7.5 with network attack vector, low complexity, no privileges, no user interaction, and availability-only impact.
Likely exposure
Exposure is most likely in systems that directly use, fork, vendor, or expose Antirez Kilo code predating the named commit. The source bundle has no CPEs or product versions, so standard asset matching may miss it.
Exploitation context
The source bundle says a remote attacker can cause denial of service. It does not provide active exploitation evidence, and KEV status is false. Treat exploit maturity as unconfirmed from these sources.
Researcher notes
The affected product metadata is incomplete: vendor, product, versions, and CPEs are all listed as `n/a`. The CWE is CWE-190, while the narrative calls it a buffer overflow, so confirm root cause against the GitHub issue and commit history.
Mitigation direction
- Identify any Antirez Kilo, forked Kilo, or vendored `kilo.c` usage.
- Update affected code to commit `7709a04ae8520c5b04d261616098cebf742f5a23` or later.
- Check the referenced GitHub issue and vendor guidance for confirmed remediation details.
- Limit remote exposure of services embedding affected Kilo-derived code where feasible.
Validation and detection
- Search software inventories for Antirez Kilo, Kilo forks, or copied `kilo.c`.
- Confirm whether deployed code predates commit `7709a04ae8520c5b04d261616098cebf742f5a23`.
- Review `editorUpdateRow` implementations in forks for equivalent vulnerable logic.
- Check availability logs for unexplained crashes in Kilo-derived components.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-20335 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/antirez/kilo/issues/60CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.