Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.3.14, 7.0.9, 7.1.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Graylog is a free and open log management platform. From 6.3.0 until 6.3.14, 7.0.9, and 7.1.4, the view update API for saved searches and dashboards permits a user with edit permission but without entity ownership to include a shareRequest that grants owner permissions to an arbitrary account. The selected account can then delete the saved search or dashboard or remove the original owner's access. Graylog Cloud was patched before the advisory was published. This issue is fixed in versions 6.3.14, 7.0.9, and 7.1.4.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Graylog2 graylog2-server
From 6.3.0 · fixed in 6.3.14; From 7.0.0 · fixed in 7.0.9; From 7.1.0 · fixed in 7.1.4
- org.graylog2:graylog2-serverMaven
From 6.3.0 · fixed in 6.3.14
- org.graylog2:graylog2-serverMaven
From 7.0.0 · fixed in 7.0.9
- org.graylog2:graylog2-serverMaven
From 7.1.0 · fixed in 7.1.4