LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19240: Embedthis GoAhead before 5.0.1 mishandles redirected HTTP requests with a large Host header.

Embedthis GoAhead before 5.0.1 mishandles redirected HTTP requests with a large Host header. The GoAhead WebsRedirect uses a static host buffer that has a limited length and can overflow. This can cause a copy of the Host header to fail, leaving that buffer uninitialized, which may leak uninitialized data in a response.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This issue affects Embedthis GoAhead web server versions before 5.0.1. A specially large Host header during redirect handling can leave memory uninitialized and cause unintended data to appear in an HTTP response. The business risk is possible information disclosure on exposed GoAhead services.

Executive priority

Prioritize remediation where GoAhead is externally reachable or protects sensitive administration paths. The severity data is incomplete, but information disclosure from a web server can support follow-on attacks if exposed data is useful.

Technical view

GoAhead WebsRedirect used a fixed-size host buffer. With an oversized Host header, the Host copy can fail, leaving the buffer uninitialized. Redirect response generation may then disclose uninitialized memory. The bundle does not provide CVSS, CWE, exploitability scoring, or specific downstream affected devices.

Likely exposure

Exposure is limited to deployments running Embedthis GoAhead before 5.0.1, especially where HTTP redirect behavior is reachable. The provided affected-product metadata is incomplete, so confirm via software inventory, SBOMs, firmware manifests, or vendor advisories.

Exploitation context

The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation. Public GitHub issues and the 5.0.1 release are available, so defenders should treat the vulnerability details as publicly known.

Researcher notes

Key uncertainty is downstream exposure. The CVE record identifies GoAhead before 5.0.1, but affected metadata is sparse. Validate version, redirect reachability, and whether the deployed vendor build includes the upstream fix without relying on product names absent from sources.

Mitigation direction

  • Upgrade Embedthis GoAhead to version 5.0.1 or a later vendor-supported release.
  • Check downstream product or firmware vendor guidance for fixed builds.
  • Restrict network access to GoAhead web interfaces where practical.
  • Prioritize internet-exposed or administrative web services first.

Validation and detection

  • Inventory applications, appliances, and firmware for Embedthis GoAhead usage.
  • Confirm no deployed GoAhead runtime is earlier than 5.0.1.
  • Review SBOMs, package manifests, or vendor release notes for fixed versions.
  • Check logs for anomalous oversized Host headers as supporting context only.
Prepared
Confidence
medium
Sources
5

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-2019-19240 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
4Source 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.