How many CVEs have patched checkActivation?

2 published CVEs changed checkActivation in nats-io/nats-server, in 2 distinct patches totalling 14 changed lines, between 2020 and 2020.

What is the latest CVE that changed checkActivation?

CVE-2020-26892 (Incorrect handling of credential expiry by /nats-io/nats-server), published 2020-11-06, changed lines 1580 of server/accounts.go.

How does checkActivation compare to the rest of nats-io/nats-server?

nats-io/nats-server has 21 CVEs with a located fix in total; 2 of them changed checkActivation.

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

nats-io/nats-server

Function

checkActivation

Name: checkActivation in nats-io/nats-server: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

server/accounts.go

Last patched November 6, 2020

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

14

Lines changed

Added plus removed

2020

Years

By CVE publication date

Overview

checkActivation in nats-io/nats-server was changed by 2 published CVE fixes in 2020, in 2 distinct patches that added or removed 14 lines in total.

nats-io/nats-server has 21 CVEs with a located fix in total, so 10% of them touched this function.

CVEs that patched it

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

Incorrect handling of credential expiry by /nats-io/nats-server
CVE-2020-26892 · line 1580 · +1 −7
Critical · CVSS 9.8
EPSS 2.3%2020-11-06
Nil dereference in NATS JWT, DoS of nats-server
CVE-2020-26521 · lines 1549–1557 · +3 −3
High · CVSS 7.5
EPSS 2.2%2020-11-06

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

Monitor nats-server CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in nats-io/nats-server changed by the most CVE fixes.

canSubscribe3 CVEs · server/client.go mqttParseConnect2 CVEs · server/mqtt.go processMsgResults2 CVEs · server/client.go processClientOrLeafAuthentication2 CVEs · server/auth.go mqttParsePub1 CVEs · server/mqtt.go mqttToNATSSubjectConversion1 CVEs · server/mqtt.go

All patched functions in nats-io/nats-server

Frequently asked questions

Common questions about CVE fixes to checkActivation.

How many CVEs have patched checkActivation?: 2 published CVEs changed checkActivation in nats-io/nats-server, in 2 distinct patches totalling 14 changed lines, between 2020 and 2020.
What is the latest CVE that changed checkActivation?: CVE-2020-26892 (Incorrect handling of credential expiry by /nats-io/nats-server), published 2020-11-06, changed lines 1580 of server/accounts.go.
How does checkActivation compare to the rest of nats-io/nats-server?: nats-io/nats-server has 21 CVEs with a located fix in total; 2 of them changed checkActivation.
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 nats-io/nats-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