LiveActive security incident?Get immediate response
CVE Record

CVE-2020-21574: Buffer overflow vulnerability in YotsuyaNight c-http v0.1.0, allows attackers to cause a denial of service...

Buffer overflow vulnerability in YotsuyaNight c-http v0.1.0, allows attackers to cause a denial of service via a long url request which is passed to the delimitedread function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-21574 describes a buffer overflow in YotsuyaNight c-http v0.1.0. A long URL request can be passed into a vulnerable read function and crash the service, causing denial of service. The public record does not provide a CVSS score, patch status, or evidence of active exploitation.

Executive priority

Treat this as a targeted availability risk. Prioritize it if c-http v0.1.0 is internet-facing or supports business-critical services; otherwise handle through normal dependency hygiene and replacement planning.

Technical view

The issue is reported as a buffer overflow in c-http v0.1.0 involving long URL input reaching the delimitedread function. The stated impact is denial of service. Public metadata lists limited affected-product detail and only one referenced GitHub issue, so exposure and remediation specifics require local verification.

Likely exposure

Exposure is likely limited to systems that directly embed or run YotsuyaNight c-http v0.1.0, especially if reachable by untrusted HTTP clients. The CVE record does not identify broader downstream products, packages, or CPEs.

Exploitation context

The source bundle does not show CISA KEV listing, confirmed active exploitation, public exploit tooling, or a vendor advisory. The described trigger is malformed input causing service denial, not confirmed remote code execution.

Researcher notes

Evidence is sparse: no CVSS vector, CWE mapping, CPE, or documented fix is included. Validate the GitHub issue details and repository history before assigning severity or declaring a patch path.

Mitigation direction

  • Check the upstream issue and repository for maintainer guidance or replacement releases.
  • Remove or isolate c-http v0.1.0 from internet-facing paths where possible.
  • Place untrusted traffic behind existing request-size controls as a compensating measure, not a confirmed vendor fix.
  • Monitor service crashes associated with unusually long URL requests.

Validation and detection

  • Search SBOMs and source trees for YotsuyaNight c-http v0.1.0 usage.
  • Confirm whether any deployed service using c-http accepts untrusted HTTP requests.
  • Review crash logs for failures correlated with oversized URL requests.
  • Use controlled non-production testing to verify long-request handling without publishing payload details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2020-21574 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.