How many CVEs have patched success?

1 published CVEs changed success in Graylog2/graylog2-server, in 2 distinct patches totalling 1 changed lines, between 2018 and 2018.

What is the latest CVE that changed success?

CVE-2018-11650 (Cross-site Scripting in Graylog Server), published 2018-06-01, changed lines 25 of graylog2-web-interface/src/util/UserNotification.js.

How does success compare to the rest of Graylog2/graylog2-server?

Graylog2/graylog2-server has 16 CVEs with a located fix in total; 1 of them changed success.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

Graylog2/graylog2-server

Function

success

Name: success in Graylog2/graylog2-server: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

graylog2-web-interface/src/util/UserNotification.js

Last patched June 1, 2018

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

1

Lines changed

Added plus removed

2018

Years

By CVE publication date

Overview

success in Graylog2/graylog2-server was changed by 1 published CVE fixes in 2018, in 2 distinct patches that added or removed 1 lines in total.

Graylog2/graylog2-server has 16 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed success, newest first, with the lines each fix touched.

Cross-site Scripting in Graylog Server
CVE-2018-11650 · line 25 · +1 −0
Medium · CVSS 6.1
EPSS 0.8%2018-06-01

Get an alert when the next CVE fix lands in Graylog2/graylog2-server, with the patched functions.

Monitor graylog2-server CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1warninggraylog2-web-interface/src/util/UserNotification.js1 CVEs · 2 patches2018

Other hotspots in the repository

Functions in Graylog2/graylog2-server changed by the most CVE fixes.

revokeToken1 CVEs · graylog2-server/src/main/java/org/graylog2/rest/resources/users/UsersResource.java toGRNType1 CVEs · graylog2-server/src/main/java/org/graylog/plugins/views/search/rest/ViewsResource.java update1 CVEs · graylog2-server/src/main/java/org/graylog/plugins/views/search/rest/ViewsResource.java duplicate1 CVEs · graylog2-server/src/main/java/org/graylog/events/rest/EventDefinitionsResource.java createView1 CVEs · graylog2-server/src/main/java/org/graylog/plugins/views/search/rest/ViewsResource.java parse1 CVEs · graylog2-server/src/main/java/org/graylog2/inputs/codecs/SyslogCodec.java

All patched functions in Graylog2/graylog2-server

Frequently asked questions

Common questions about CVE fixes to success.

How many CVEs have patched success?: 1 published CVEs changed success in Graylog2/graylog2-server, in 2 distinct patches totalling 1 changed lines, between 2018 and 2018.
What is the latest CVE that changed success?: CVE-2018-11650 (Cross-site Scripting in Graylog Server), published 2018-06-01, changed lines 25 of graylog2-web-interface/src/util/UserNotification.js.
How does success compare to the rest of Graylog2/graylog2-server?: Graylog2/graylog2-server has 16 CVEs with a located fix in total; 1 of them changed success.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track Graylog2/graylog2-server CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing