Session hijacking via audit-log identifier exposure
Published Jul 31, 2021 · Updated Aug 4, 2024
Sensitive data exposure in Graylog before 4.1.2 allows attackers to hijack sessions through identifiers written to its audit log. Graylog's Enterprise Audit Log records session IDs instead of excluding authentication material, exposing active and previously active IDs to attackers able to read its entries. By default, the log resides in the local database and is restricted to administrators; a stolen ID grants only its owner's permissions.
Summary
What happened
Sensitive data exposure in Graylog before 4.1.2 allows attackers to hijack sessions through identifiers written to its audit log. Graylog's Enterprise Audit Log records session IDs instead of excluding authentication material, exposing active and previously active IDs to attackers able to read its entries. By default, the log resides in the local database and is restricted to administrators; a stolen ID grants only its owner's permissions.
The record
- CVE
- CVE-2021-37760
- Published
- Jul 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-532, T1550
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo