CVE-2021-37760
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Session ID leak in the audit log in Graylog before 4.1.2 allows attackers to escalate privileges (to the access level of the leaked session ID).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGraylog before version 4.1.2 has a vulnerability where session IDs are inadvertently written to the audit log. An attacker with access to the audit log can extract these session IDs and use them to hijack sessions, escalating privileges to match the compromised session's access level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.1.1, < 4.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Graylog versionRun the command to display the Graylog server version (typically `graylog-ctl version` or check the web interface under System > Nodes).Affected if The installed version is greater than or equal to 2.1.1 and less than 4.1.2.
-
Verify audit logging is enabledAccess the Graylog configuration file or web interface to confirm whether the audit log feature is turned on.Affected if Audit logging is enabled and the Graylog version falls within the affected range.
-
Locate the audit log filesIdentify where Graylog stores audit logs, typically in the configured log directory.Affected if Audit logs exist and contain entries from a Graylog version in the affected range.
-
Inspect audit log for session dataOpen or search the audit log file and look for entries that may contain session identifiers or tokens.Affected if The audit log contains visible session IDs or authentication tokens.
You are affected if your Graylog version is between 2.1.1 and 4.1.2 (exclusive) and audit logging is enabled, with any evidence of session IDs present in the audit logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.1.2
Upgrade Graylog to version 4.1.2 or later, which addresses the session ID leakage in the audit log. Additionally, restrict access to audit logs to trusted administrators only as a defense-in-depth measure.
Graylog 4.1.2 or later (e.g., latest stable 4.x or 5.x release)
- 1. Back up your Graylog configuration and data before proceeding with the upgrade.
- 2. Review the Graylog upgrade documentation for your current version to ensure compatibility.
- 3. Stop the Graylog service.
- 4. Upgrade Graylog to version 4.1.2 or later (e.g., 4.1.2, 4.2.x, or latest stable release).
- 5. Verify the upgrade was successful by checking that the audit log no longer contains session IDs.
- 6. Restart the Graylog service.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37760 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data