LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41732: An issue was discovered in zeek version 4.1.0.

An issue was discovered in zeek version 4.1.0. There is a HTTP request splitting vulnerability that will invalidate any ZEEK HTTP based security analysis. NOTE: the vendor's position is that the observed behavior is intended

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE concerns Zeek 4.1.0 network monitoring. A crafted HTTP parsing condition could make Zeek’s HTTP-based security analysis unreliable, meaning monitoring may miss or misclassify activity. The vendor reportedly considers the behavior intended, so operational risk depends on how much the organization relies on Zeek HTTP analysis.

Executive priority

Prioritize assessment where Zeek is a primary network detection control. The business issue is not data theft by itself, but confidence in HTTP monitoring and alert integrity.

Technical view

The record describes a CWE-444 HTTP request splitting issue in Zeek 4.1.0 with CVSS 8.2. It is network-reachable, unauthenticated, and low complexity. The stated impact is invalidation of Zeek HTTP-based analysis, with low confidentiality and high integrity impact. Affected-product metadata is incomplete.

Likely exposure

Exposure is most likely where Zeek 4.1.0 is deployed for HTTP traffic analysis or alerting. The bundle does not prove broader affected versions or products.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk is primarily detection bypass or analysis integrity loss in environments relying on Zeek HTTP telemetry.

Researcher notes

Evidence is narrow: the CVE description names Zeek 4.1.0, while affected vendor/product fields are n/a. The vendor-disputed behavior reduces certainty around remediation. Treat version scope, exploitability, and fixes as unconfirmed beyond the cited sources.

Mitigation direction

  • Inventory Zeek deployments and identify any Zeek 4.1.0 instances.
  • Review the referenced Zeek issue and current vendor guidance.
  • Avoid relying solely on Zeek HTTP analysis for critical detections.
  • Use compensating telemetry where HTTP monitoring integrity matters.
  • Document any accepted risk if vendor guidance treats behavior as intended.

Validation and detection

  • Confirm deployed Zeek versions and HTTP analyzer usage.
  • Review detection rules that depend on Zeek HTTP event interpretation.
  • Compare Zeek HTTP telemetry against another trusted network sensor.
  • Check whether internal tests cover ambiguous HTTP parsing behavior.
  • Record whether vendor guidance changes operational assumptions.
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.

cwe · low confidence lookup

CWE-444: 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 lookup
cve · low confidence lookup

CVE-2021-41732 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
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N3.94.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2021-41732Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-444 · source CWE mapping

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.