Security readout for executives and security teams
Plain-English summary
Older Zulip Server installations could briefly expose RabbitMQ management-related ports with a weak default secret. If those ports were reachable from outside, an unauthenticated remote attacker could potentially access internal message traffic and run code as the RabbitMQ user.
Executive priority
Treat as high priority for any self-hosted Zulip deployment below 4.9. The business risk is unauthorized access to internal collaboration traffic and limited server-side code execution if RabbitMQ ports were reachable externally.
Technical view
Zulip Server before 4.9 failed during initial installation to restrict RabbitMQ ports until first reboot or RabbitMQ restart. The Erlang cookie protecting port 25672 used weak randomness, estimated around 20 bits of practical entropy. Exposure requires missing OS or network firewall protection.
Likely exposure
Most relevant to self-hosted Zulip Server versions before 4.9, especially newly installed systems before reboot or RabbitMQ restart. Internet exposure depends on whether TCP ports 5672 or 25672 were reachable through host firewalls, cloud security groups, or network perimeter rules.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The advisory describes unauthenticated remote brute forcing when port 25672 is exposed, with possible code execution as rabbitmq and visibility into message traffic.
Researcher notes
The vulnerability is conditional: weak RabbitMQ cookie entropy matters only when RabbitMQ distribution or AMQP ports are exposed beyond the Zulip host. Evidence supports the affected window, affected version range, CVSS 8.6, and fixed version 4.9; active exploitation is not established.
Mitigation direction
- Upgrade Zulip Server to version 4.9 or later.
- Block external access to RabbitMQ ports 5672 and 25672.
- Confirm host and network firewalls restrict RabbitMQ to trusted paths.
- Review Zulip advisory before relying on operational workarounds.
Validation and detection
- Inventory all Zulip Server deployments and identify versions below 4.9.
- Check firewall and cloud rules for external access to ports 5672 and 25672.
- Review deployment timelines for the initial-installation exposure window.
- Assess RabbitMQ logs and message confidentiality where exposure existed.
- Confirm upgraded systems are running the patched Zulip release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-338: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-43799 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zulip/zulip/security/advisories/GHSA-p663-wxvv-2fjpCVE reference · x_refsource_CONFIRM
- https://github.com/zulip/zulip/commit/a5496f4098e3998c9b84e8dc564aa983d6cdf6e8CVE reference · x_refsource_MISC
- https://github.com/gteissier/erl-matterCVE reference · x_refsource_MISC
- https://github.com/zulip/zulip/releases/tag/4.9CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.