Zeek

zeek.org
Zeek

Zeek (formally Bro) Passively monitors network traffic and looks for suspicious activity.

Open Source

Zeek Source Code

Author

zeek

Description

Zeek is a powerful network analysis framework that is much different from the typical IDS you may know.

#bro#dfir#ndr#network-monitoring#nsm#pcap#security#zeek

Homepage

https://www.zeek.org

Repository

  • LicenseOther
  • Created06 Jul 12
  • Primary languageC++
  • Size284,815 KB
  • Stars8,219
  • Forks1,456
  • Watchers8,219

Language Usage

Language Usage

Project Health

  • Last commit10 hours ago
  • Open issues265
  • Latest releasev9.1.0-dev

Recent Commits

  • Arne Welzel(11 Nov 26)

    Merge branch 'dns-answer-context' of https://github.com/aditya226-sharma/zeek * 'dns-answer-context' of https://github.com/aditya226-sharma/zeek: DNS: log CAA, HINFO, SVCB, and HTTPS answers

  • zeek-bot(11 Nov 26)

    Docs: Regenerated via GitHub workflow [nomail] [skip ci]

  • Arne Welzel(10 Nov 26)

    Merge remote-tracking branch 'origin/topic/awelzel/skip-zeromq-overload-logging-on-windows' * origin/topic/awelzel/skip-zeromq-overload-logging-on-windows: btest/cluster/zeromq: Skip overload-logging on windows

  • Tim Wojtulewicz(10 Nov 26)

    Merge remote-tracking branch 'origin/dependabot/github_actions/github/codeql-action/upload-sarif-4.39.3' * origin/dependabot/github_actions/github/codeql-action/upload-sarif-4.39.3: build(deps): bump github/codeql-action/upload-sarif

  • Tim Wojtulewicz(10 Nov 26)

    Merge remote-tracking branch 'origin/dependabot/github_actions/docker/login-action-4.8.0' * origin/dependabot/github_actions/docker/login-action-4.8.0: build(deps): bump docker/login-action from 4.7.0 to 4.8.0

  • Evan Typanski(10 Nov 26)

    Merge remote-tracking branch 'origin/topic/etyp/bye-checksums' * origin/topic/etyp/bye-checksums: Analyze packets with bad checksums by default btest: Fix bad checksums in test traces

  • Evan Typanski(09 Nov 26)

    Analyze packets with bad checksums by default Fixes #5294 More discussion at #4947 Packets with invalid checksums used to not get analyzed. This mainly appeared when monitoring local traffic, where NIC checksum offloading caused missing packets. But, we can't just set `ignore_checksums=T` like #5295 because we would likely still want `c`/`C` in the conn history and the weirds. This also adds `drop_bad_checksums`. If you want the old behavior, set that to true. Also, IPv4 packets with a total length of zero are analyzed by default using capture length (this is what ignore_checksums would do before). Co-Authored-By: Claude Opus 5.5 <[email protected]>

  • Evan Typanski(10 Nov 26)

    Merge branch 'pcap-activate-warnings' of https://github.com/Oluwatobi-Mustapha/zeek * 'pcap-activate-warnings' of https://github.com/Oluwatobi-Mustapha/zeek: pcap: Handle activation warnings

  • dependabot[bot](10 Nov 26)

    build(deps): bump docker/login-action from 4.7.0 to 4.8.0 Bumps [docker/login-action](https://github.com/docker/login-action) from 4.7.0 to 4.8.0. - [Release notes](https://github.com/docker/login-action/releases) - [Commits](https://github.com/docker/login-action/compare/81c6f93d4bc991e510b342a00b419b3bb4efc5c6...8aa5831fb8d48d8f76594c7ddde61ae58019f550) --- updated-dependencies: - dependency-name: docker/login-action dependency-version: 4.8.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

  • dependabot[bot](10 Nov 26)

    build(deps): bump github/codeql-action/upload-sarif Bumps [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) from 4.39.1 to 4.39.3. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/9b3254085494b55a0f7c4c2b3d2d52cc712ce370...33d7b85da1a04171e211befe2c739303b9a4c066) --- updated-dependencies: - dependency-name: github/codeql-action/upload-sarif dependency-version: 4.39.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>

  • Arne Welzel(10 Nov 26)

    btest/cluster/zeromq: Skip overload-logging on windows Definitely a cop-out, but we already skip overload-drop.zeek and overload-worker-proxy-topic-drop.zeek on Windows, so add this, too.

  • Aditya Sharma(10 Nov 26)

    DNS: log CAA, HINFO, SVCB, and HTTPS answers The dns.log "answers" and "TTLs" fields were empty for CAA, HINFO, SVCB, and HTTPS resource records. These record types were already parsed and exposed through their corresponding dns_* events, but they lacked an event handler that calls the DNS::do_reply() hook, which is what populates the per-answer summaries used by the logging framework. Add handlers for dns_CAA_reply, dns_HINFO_reply, dns_SVCB, and dns_HTTPS that pass a short answer string to DNS::do_reply(). The TTL alignment with "answers" is preserved because do_reply() appends the TTL alongside the string. For SVCB and HTTPS, the answer includes the priority before the target name so records with different priorities remain distinguishable. Extend the existing CAA, HINFO, SVCB, and HTTPS btests to compare the full dns.log output, and add the corresponding baselines. Fixes #5467.

  • Arne Welzel(10 Nov 26)

    Merge remote-tracking branch 'origin/topic/awelzel/zeromq-log-drops-metric' * origin/topic/awelzel/zeromq-log-drops-metric: cluster/zeromq: Fix reporting of dropped log writes, add metric

  • Arne Welzel(05 Nov 26)

    cluster/zeromq: Fix reporting of dropped log writes, add metric When the HWM for the log PUSH socket runs full, Zeek currently reports every dropped log message via reporter->Error(). There also is a metric missing. Address both these shortcomings and add a test. Instead of just outputting to stderr once, it'd be nice log this every so often here continuously. In a separate PR, there's a ``ReportOnceEvery`` helper class in the works that would allow for that. For now, use the same pattern as for the XPUB socket. Removes the XXX comment as dropping has been the policy so far anyhow and this now adds a metric for observability.

  • Tim Wojtulewicz(10 Nov 26)

    Merge remote-tracking branch 'sotomayorlucas/fix/rdp-tpkt-version' * sotomayorlucas/fix/rdp-tpkt-version: RDP: reject a TPKT header whose version is not 3

  • Evan Typanski(09 Nov 26)

    Merge branch 'topic/spryzz3n/5931-empty-record-separator' of https://github.com/spryzz3n/zeek * 'topic/spryzz3n/5931-empty-record-separator' of https://github.com/spryzz3n/zeek: Reject empty record_separator in raw input reader

  • Evan Typanski(09 Nov 26)

    btest: Fix bad checksums in test traces The next commit is going to change checksum behavior. These traces all had invalid checksums (probably from checksum offloading). This just recomputes them (and corresponding baseline updates from those packets). Co-Authored-By: Claude Opus 5.5 <[email protected]>

  • Oluwatobi Mustapha(08 Nov 26)

    pcap: Handle activation warnings

  • spryzz3n(06 Nov 26)

    Reject empty record_separator in raw input reader An empty separator causes the raw reader to keep producing empty records instead of making progress. Add a check to reject empty separators during initialization, update the documentation, and add a regression test for this case. Fixes #5931

  • Lucas Sotomayor(06 Nov 26)

    RDP: reject a TPKT header whose version is not 3 The TPKT record read the version octet but never checked it, so a Connection Request with a TPKT version other than 3 was parsed and logged as an RDP connection. RFC 1006 defines only version 3, and the servers we tried (xrdp, FreeRDP) do not answer such a request. Enforce version == 3, so the analyzer reports a protocol violation instead. In rdp-invalid-length, a later misaligned PDU now fails on the TPKT version instead of on the Connect Confirm record type. Co-Authored-By: Claude Opus 5.5 <[email protected]>

  • Tim Wojtulewicz(05 Nov 26)

    Remove stray curly brace in ci/test.sh

  • Arne Welzel(05 Nov 26)

    Merge remote-tracking branch 'origin/topic/awelzel/systemd-generator-continuation-fixes' * origin/topic/awelzel/systemd-generator-continuation-fixes: tools/systemd-generator: Fixes and hardening around continuation

  • Tim Wojtulewicz(05 Nov 26)

    Fix pre-commit ruff-format issues from earlier merges

  • Tim Wojtulewicz(05 Nov 26)

    Merge remote-tracking branch 'sotomayorlucas/fix/dnp3-g4-variations' * sotomayorlucas/fix/dnp3-g4-variations: DNP3: fix the object sizes of double-bit binary input events (g4)

  • Tim Wojtulewicz(05 Nov 26)

    Merge remote-tracking branch 'sotomayorlucas/fix/dnp3-g3v1-packed' * sotomayorlucas/fix/dnp3-g3v1-packed: DNP3: parse packed double-bit binary inputs (g3v1) by size

  • Tim Wojtulewicz(05 Nov 26)

    Merge remote-tracking branch 'sotomayorlucas/fix/dnp3-g41-request' * sotomayorlucas/fix/dnp3-g41-request: DNP3: parse analog output blocks (g41) in requests

  • Tim Wojtulewicz(05 Nov 26)

    Merge remote-tracking branch 'origin/topic/timw/bail-out-of-tests-early-on-failures' * origin/topic/timw/bail-out-of-tests-early-on-failures: CI: Stop running unit tests separately CI: Bail out of tests early after first failure

  • Arne Welzel(05 Nov 26)

    tools/systemd-generator: Fixes and hardening around continuation Used the generator a bit and had a long list of args and wanted to comment some of them out, only to find that an indented commented line would be part of the ExecStart line. Further, make a blank/empty lines after a continuation finish the current option, so that an indented line after is reported as an error, rather than considered part of the previous option. And, pre-check continuations to avoid raising a std::logic_error when accessing option.Value() as is already beeing done when parsing the interface sections.

  • Tim Wojtulewicz(04 Nov 26)

    CI: Stop running unit tests separately These are run by the core.doctests btest already

  • Tim Wojtulewicz(03 Nov 26)

    CI: Bail out of tests early after first failure

Zeek Security

6.9/10

Repo Security Summary

Updated 24 Aug 26 Fuzz tested

  • Code-Review6/10
  • Maintained10/10
  • CII-Best-Practices0/10
  • License9/10
  • Security-Policy9/10
  • Branch-ProtectionN/A
  • Dangerous-Workflow10/10
  • Signed-Releases8/10
  • Token-Permissions0/10
  • Packaging10/10
  • Fuzzing10/10
  • SAST0/10
  • Binary-Artifacts10/10
  • Pinned-Dependencies2/10

Security Advisories (74)

  • mediumPatched

    GHSA-85jg-jxjg-3rvhGTPv1: IP length underflow causes out-of-bounds read

  • mediumPatched

    GHSA-q2jp-3x4p-fp6cFile Analysis: Memory exhaustion via tiny non-contiguous blocks

  • highPatched

    GHSA-rmv9-rq35-fw28SSL: Unbounded certificate state growth

  • highPatched

    GHSA-2q7f-wp5q-4jh5KRB: Unbounded array and element state growth

  • highPatched

    GHSA-5jww-j993-whw5MIME Headers can bypass line limits

  • mediumPatched

    GHSA-rr24-3xvr-v648HTTP: Multi-part transfer-encoding headers not handled correctly

  • highPatched

    GHSA-gxg9-7vfv-qq5fReassembler memory amplificiation for blocks after a hole

  • mediumPatched

    GHSA-cg6p-j73j-76jmSMTP/MIME: Signed integer overflow

  • highPatched

    GHSA-v6w4-3pj6-p4chDNP3: Large application layer fragment resource exhaustion

  • mediumPatched

    GHSA-256v-q24v-rm42Unbounded Connection history member growth

  • mediumPatched

    GHSA-234h-hf84-23g5Modbus: Unbounded state growth in track-memmap policy script

  • mediumPatched

    GHSA-p7wh-94mw-76hvtcp: Content extraction reads beyond truncated captures

  • highPatched

    GHSA-5x3v-rp68-7789DTLS: Partial handshake memory exhaustion

  • highPatched

    GHSA-3pcv-3q53-4vf6DNS: Resource exhaustion via TXT RR holding many empty character strings

  • highPatched

    GHSA-vg68-x8g9-5wg9PE: Excessive numbers of sections allocates large amounts of memory

  • highPatched

    GHSA-v2hr-vp3r-q7m2DNS/TCP: Eager memory allocation for messages

  • mediumPatched

    GHSA-gm23-j78v-rcr8BitTorrent: Memory leak without handlers

  • mediumPatched

    GHSA-qwfc-r652-34m7SMB: Various state growth issues

  • highPatched

    GHSA-j2wq-86vc-93cgTLS: Unbounded extensions could exhaust parser memory

  • highPatched

    GHSA-fch4-9qmm-454rFinger: Excessive whitespace in requests could exhaust parser memory

  • highPatched

    GHSA-prm9-9w6q-xg34HTTP: Unbounded unanswered_requests queue growth

  • highPatched

    GHSA-2prg-45gv-3rg9IMAP: Unbounded capability parsing

  • highPatched

    GHSA-xvj8-9xvq-g5qqMIME: Folded header lines amplify persistent parser state

  • highPatched

    GHSA-5mcr-v3f9-r9xmRDP: Large numbers of client-channel events can exhaust memory

  • highPatched

    GHSA-xc4c-h8m4-m827Websocket: Many small unfinished continuation frames allocate lots of memory

  • highPatched

    GHSA-cxjj-9x4p-4485SIP: SIP over UDP uses large amounts of memory for large packet sequences

  • mediumPatched

    GHSA-rg94-q747-pcjgHTTP: Analysis evasion for prefixes of CONNECT and HEAD method strings

  • highPatched

    GHSA-x38g-wp8h-rfrfRDP: Connections with many small x509 certificates result in excessive memory usage

  • mediumPatched

    GHSA-rx99-gxqp-gm4wDNS: WKS RRs cause other RRs to be hidden in logs

  • highPatched

    GHSA-57g4-pwfx-wcj3krb: PKINIT values multiply into file-analysis state

  • highPatched

    GHSA-pwfv-247f-jfrhVarious event queue memory exhaustion vulnerabilities

  • highPatched

    GHSA-vhc3-782q-hqjjX509/OCSP: Unbounded memory growth when parsing data

  • highPatched

    GHSA-8xr9-cgwc-52gxRPC: Small messages allocate large amounts of unnecessary memory

  • highPatched

    GHSA-694c-w947-hm9jMIME: Analyzer allows headers to grow without bound in HTTP/SMTP

  • highPatched

    GHSA-m754-q884-jrv4MQTT: Analyzer allows unbounded pending subscriptions and topics per subscription

  • highPatched

    GHSA-5xvw-rv8q-7gh7GSSAPI: Memory exhaustion when reading SPNEGO NegTokenResp packets

  • highPatched

    GHSA-42p8-pr85-r6cjKRB: Memory exhaustion when reading AS-REQ packets

  • mediumPatched

    GHSA-mr9q-gg3p-g8x9NCP: Potential excessive memory allocation

  • highPatched

    GHSA-j24f-fcr2-2fj4NTLM: Use target-info lengths to limit parsing Challenge messages

  • highPatched

    GHSA-64hr-73cp-g768ldap: Unbounded memory growth in aggregate ASN.1 messages

  • highPatched

    GHSA-5695-9qhq-wmmjQUIC: Eager resource allocation for non-QUIC traffic can exhaust process memory

  • highPatched

    GHSA-gr64-qgpv-2xgmQUIC: Unbounded memory growth for sparse crypto frames

  • highPatched

    GHSA-5xxm-w466-8ghxTCP: Reassembly algorithm doesn't handle excessive overlapping blocks cleanly

  • highPatched

    GHSA-378g-pcg9-x2hrMySQL: COM_QUERY attribute memory exhaustion

  • highPatched

    GHSA-7cf3-cq69-g7p6zip: Use-after-free crash from HTTP gzip-encoded multipart bodies

  • highPatched

    GHSA-jmgg-6f63-qccpSOCKS: Nested SOCKS tunnels can cause memory/stack exhaustion

  • highPatched

    GHSA-5wp3-97xw-6793LDAP: Quadratic-time algorithm handling SearchFilter fields

  • highPatched

    GHSA-4vgp-xwjx-mc87PostgreSQL: identified response fields exhaust memory and CPU

  • mediumPatched

    GHSA-mjr9-ghf8-79gjUse-after-free bug through PacketAnalyzer::Geneve::get_options() due to IP fragment reassembly

  • highPatched

    GHSA-2xc9-g36m-w7jhSMB: Chains of AndX messages can crash Zeek

  • highPatched

    GHSA-px95-jfxw-4jw2DNP3: Memory exhaustion via file control (g70v1) fields

  • highPatched

    GHSA-wjf9-326g-m9h3SIP: Memory exhaustion from long request/response paths

  • highPatched

    GHSA-hxj7-pcq9-c949DHCP: Memory exhaustion from retained options after analyzer violation

  • highPatched

    GHSA-49x5-fmqq-4ccvSMTP: Memory exhaustion from large numbers of rcptto/to/cc/path entries

  • mediumPatched

    GHSA-qjhc-rfmf-3vgpTelnet: AUTH STATUS options before a NAME is received results in event argument mismatch

  • highPatched

    GHSA-rmc2-mqq6-wcw9SMB: DCE/RPC memory exhaustion from fragment state

  • mediumPatched

    GHSA-q48f-3qm2-j875UDP: udp_contents events could trigger out-of-bounds reads

  • highPatched

    GHSA-3gxr-8f49-vrgrAnalyzer manager: Equivalent scheduled analyzers could exhaust memory

  • mediumPatched

    GHSA-gq9q-85wf-mq48NetBIOS: Memory exhaustion from declared session lengths

  • highPatched

    GHSA-2prm-q48h-m96wZIP: Unbounded decompression

  • highPatched

    GHSA-c573-w89f-fpxmRedis: Parsed Redis traffic memory exhaustion

  • highPatched

    GHSA-84jg-cwr7-4p6wInvalid IPv6 fragments can lead to unbounded state growth

  • highPatched

    GHSA-5v93-pm35-5mq6SSH: Quadratic KEX algorithm CPU exhaustion

  • highPatched

    GHSA-hww6-p5xp-6rqvNVT: Oversized line recovery writes before heap buffer

  • highPatched

    GHSA-qf53-234m-7vhqDHCP: Unbounded state growth via join_data

  • highPatched

    GHSA-9m23-gwjx-p3j8FTP: Unbounded state growth via ftp_data_expected

  • highPatched

    GHSA-j48p-9pm3-pgpxOCSP: Empty byName responder ID crashes Zeek

  • highPatched

    GHSA-924m-g9gv-45xcARP: Tunneled ARP traffic crashes Zeek

  • mediumPatched

    GHSA-6566-755c-7mwqIRC: Single DCC Send packet can result in scripting error

  • mediumPatched

    GHSA-q6c5-95ff-cwr9IRC: Invalid DCC Send host/port fields can lead to unexpected parsing results

  • highPatched

    GHSA-pxc9-fc9v-r39qLDAP: Unbounded per-connection script state

  • highPatched

    GHSA-5h5v-fcxr-f223IRC DCC SEND has unbounded state growth

  • highPatched

    GHSA-72qh-gpq9-cj8wtunnel_changed event limit bypass on direct/tunneled toggles

  • highPatched

    GHSA-vh6p-7vxf-m7rhRecursive stack exhaustion from deep packet analyzer chains

Zeek Website

Website

Zeek: The Open Source Network Monitor

The Open Source Network Monitor Flexible, scriptable, and powered by defenders. Get Zeek View on GitHub About Zeek Zeek and Ye Shall Find Zeek has been a cornerstone of the open-source and cybersecurity communities for decades. Originally developed by Vern Paxson in the 1990s under the name "Bro," Zeek was designed to provide deep insights…

Redirects

Does not redirect

Security Checks

All 65 security checks passed

Server Details

  • IP Address192.0.78.212
  • LocationSan Francisco,California,United States of America,NA
  • ISPAutomattic Inc
  • ASNAS2635

Associated Countries

  • USUS
  • CACA
  • JPJP

Safety Score

Website marked as safe

100%

Trackers

No known trackers found

Blacklist Check

zeek.org was found on 0 blacklists

  • AntiSocial Blacklist
  • Artists Against 419
  • Badbitcoin
  • Bambenek Consulting
  • CERT Polska
  • CoinBlockerLists
  • CRDF
  • CryptoScamDB
  • EtherAddressLookup
  • EtherScamDB
  • Fake Website Buster
  • MetaMask EthPhishing
  • NABP Not Recommended Sites
  • OpenPhish
  • PetScams
  • PhishFeed
  • PhishFort
  • Phishing.Database
  • PhishStats
  • PhishTank
  • Phishunt
  • RPiList Not Serious
  • Scam.Directory
  • SecureReload Phishing List
  • Spam404
  • StopGunScams
  • Suspicious Hosting IP
  • ThreatFox
  • ThreatLog
  • TweetFeed
  • URLhaus
  • ViriBack C2 Tracker

Website Preview

Website preview

Zeek Reviews

More Intrusion Detection

  • An 802.11 layer2 wireless network detector, sniffer, and intrusion detection system.

  • OSSEC is an Open Source host-based intrusion detection system, that performs log analysis, integrity checking, monitoring, rootkit detection, real-time alerting and active response.

  • picosnitch helps protect your security and privacy by "snitching" on anything that connects to the internet, letting you know when, how much data was transferred, and to where. It uses BPF to monitor network traffic per application, and per parent to cover those that just call others. It also hashes every executable, and will complain if some mischievous program is giving it trouble.

  • SNARE (System iNtrusion Analysis and Reporting Environment) is a series of log collection agents that facilitate centralized analysis of audit log data. Logs from the OS are collected and audited. Full remote access, through a web interface easy to use manually, or by an automated process.

    Not Open Source

About the Data: Zeek

Edit Zeek Data

You can edit Zeek's entry in this section of awesome-privacy.yml by submitting a PR to our GitHub repo.
Note that some of the information shown above has been aggregated from external sources, a list of these can be found data documentation.

Origin Data

Modify Data

API

You can access Zeek's data programmatically via our API. Simply make a GET request to:

https://api.awesome-privacy.xyz/v1/services/zeek

The REST API is free, no-auth and CORS-enabled. To learn more, view the API Docs or read the API Usage Guide.

Share Zeek

Help your friends compare Intrusion Detection, and pick privacy-respecting software and services.
Share Zeek and Awesome Privacy with your network!