org.graylog2:graylog2-server vulnerabilities
Graylog
- Registry
- Maven
- Latest
- 7.2.2
16 known advisories
The latest version, 7.2.2, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=7.2.2 -DforceVersion=trueIs your project on an affected org.graylog2:graylog2-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.graylog2:graylog2-server
Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards
- Affected
- >=6.3.0 <6.3.14 · >=7.0.0 <7.0.9 · >=7.1.0 <7.1.4
- Fixed in
- 6.3.14, 7.0.9, 7.1.4
Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens
- Affected
- >=6.2.0 <6.3.12 · >=7.0.0 <7.0.7 · >=7.1.0 <7.1.2
- Fixed in
- 6.3.12, 7.0.7, 7.1.2
Fortigate syslog message parser can be exploited to modify or delete fields from the original message
- Affected
- <6.3.12 · >=7.0.0 <7.0.7 · >=7.1.0 <7.1.2
- Fixed in
- 6.3.12, 7.0.7, 7.1.2
Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fields
- Affected
- >=7.1.0 <7.1.4
- Fixed in
- 7.1.4
Graylog vulnerable to privilege escalation through API tokens
- Affected
- >=6.2.0 <6.2.4 · >=6.3.0-alpha.1 <6.3.0-rc.2
- Fixed in
- 6.2.4, 6.3.0-rc.2
Graylog Allows Session Takeover via Insufficient HTML Sanitization
- Affected
- <6.0.14 · >=6.1.0 <6.1.10
- Fixed in
- 6.0.14, 6.1.10
Graylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser
- Affected
- <6.2.0
- Fixed in
- 6.2.0
Graylog's Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong value
- Affected
- >=6.1.0 <6.1.9
- Fixed in
- 6.1.9
Graylog session fixation vulnerability through cookie injection
- Affected
- >=4.3.0 <5.1.11 · >=5.2.0-alpha.1 <5.2.4
- Fixed in
- 5.1.11, 5.2.4
Graylog vulnerable to instantiation of arbitrary classes triggered by API request
- Affected
- >=2.0.0 <5.1.11 · >=5.2.0-alpha.1 <5.2.4
- Fixed in
- 5.1.11, 5.2.4
Graylog server has partial path traversal vulnerability in Support Bundle feature
- Affected
- >=5.1.0 <5.1.3
- Fixed in
- 5.1.3
Graylog vulnerable to insecure source port usage for DNS queries
- Affected
- >=5.1.0 <5.1.3 · <5.0.9
- Fixed in
- 5.0.9, 5.1.3
Graylog user session is still usable after logout
- Affected
- >=1.0 <5.0.9 · >=5.1.0 <5.1.3
- Fixed in
- 5.0.9, 5.1.3
Cross-site Scripting in Graylog
- Affected
- <2.4.4
- Fixed in
- 2.4.4
Cross-site Scripting in Graylog Server
- Affected
- <2.4.4
- Fixed in
- 2.4.4
Cross-site Scripting in Graylog Server
- Affected
- <2.4.6
- Fixed in
- 2.4.6
Is your org.graylog2:graylog2-server version vulnerable?
- org.graylog2:graylog2-server 7.2No known advisories in 7.2.2
- org.graylog2:graylog2-server 7.1No known advisories in 7.1.12
- org.graylog2:graylog2-server 7.0No known advisories in 7.0.16
- org.graylog2:graylog2-server 6.3No known advisories in 6.3.15
- org.graylog2:graylog2-server 6.22 advisories in 6.2.14
- org.graylog2:graylog2-server 6.12 advisories in 6.1.16
- org.graylog2:graylog2-server 6.02 advisories in 6.0.14
- org.graylog2:graylog2-server 5.23 advisories in 5.2.12
- org.graylog2:graylog2-server 5.13 advisories in 5.1.13
- org.graylog2:graylog2-server 5.05 advisories in 5.0.13
Which of your client projects still run an old org.graylog2:graylog2-server?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.