LiveActive security incident?Get immediate response
CVE Record

CVE-2019-12175: In Zeek Network Security Monitor (formerly known as Bro) before 2.6.2, a NULL pointer dereference in the Ke...

In Zeek Network Security Monitor (formerly known as Bro) before 2.6.2, a NULL pointer dereference in the Kerberos (aka KRB) protocol parser leads to DoS because a case-type index is mishandled.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can crash Zeek/Bro network monitoring when it parses certain Kerberos traffic. The business risk is loss of network security visibility, not data theft or remote code execution based on the provided sources.

Executive priority

Treat this as a visibility and resilience issue. Patch affected sensors in normal security maintenance unless Zeek outages are already affecting detection coverage.

Technical view

CVE-2019-12175 is a NULL pointer dereference in the Zeek Kerberos protocol parser before version 2.6.2. The CVE says a mishandled case-type index can cause denial of service.

Likely exposure

Exposure is likely limited to organizations running Zeek/Bro versions earlier than 2.6.2 where sensors process Kerberos traffic. The source bundle does not provide CPEs or detailed affected version ranges.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The described impact is denial of service through parser crash behavior.

Researcher notes

The public bundle names the root cause and fixed-before boundary but lacks CVSS, CWE, CPE, detailed advisory text, and exploit evidence. Avoid assuming broader product impact beyond Zeek/Bro before 2.6.2.

Mitigation direction

  • Upgrade Zeek/Bro deployments to version 2.6.2 or later.
  • Review Zeek release notes and vendor guidance for deployment-specific instructions.
  • Prioritize sensors monitoring authentication-heavy network segments.
  • Ensure monitoring coverage remains available during upgrade windows.

Validation and detection

  • Inventory Zeek/Bro versions across all sensors and collectors.
  • Confirm no production sensor remains below version 2.6.2.
  • Check whether Kerberos protocol parsing is active in monitored environments.
  • Review recent Zeek crashes for correlation with Kerberos traffic.
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-2019-12175 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.