How many CVEs have patched ServiceTester?

1 published CVEs changed ServiceTester in authzed/spicedb, in 1 distinct patches totalling 2 changed lines, between 2024 and 2024.

What is the latest CVE that changed ServiceTester?

CVE-2024-48909 (SpiceDB calls to LookupResources using LookupResources2 with caveats may return context is missing when it is not), published 2024-10-14, changed lines 31 of internal/services/integrationtesting/consistencytestutil/servicetester.go.

How does ServiceTester compare to the rest of authzed/spicedb?

authzed/spicedb has 14 CVEs with a located fix in total; 1 of them changed ServiceTester.

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

authzed/spicedb

Type

ServiceTester

Name: ServiceTester in authzed/spicedb: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

internal/services/integrationtesting/consistencytestutil/servicetester.go

Last patched October 14, 2024

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

ServiceTester in authzed/spicedb was changed by 1 published CVE fixes in 2024, in 1 distinct patches that added or removed 2 lines in total.

authzed/spicedb has 14 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

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

SpiceDB calls to LookupResources using LookupResources2 with caveats may return context is missing when it is not
CVE-2024-48909 · line 31 · +1 −1
Low · CVSS 2.4
EPSS 0.3%2024-10-14

Get an alert when the next CVE fix lands in authzed/spicedb, with the patched functions.

Monitor spicedb CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1LookupResourcesinternal/services/integrationtesting/consistencytestutil/servicetester.go1 CVEs · 1 patches2024

Other hotspots in the repository

Functions in authzed/spicedb changed by the most CVE fixes.

checkRequestToKey1 CVEs · internal/dispatch/keys/computed.go lookupResourcesRequest2ToKey1 CVEs · internal/dispatch/keys/computed.go computeCallHash1 CVEs · internal/services/v1/hash.go LookupResources2DispatchKey1 CVEs · internal/dispatch/keys/keys.go LookupResources2CacheKey1 CVEs · internal/dispatch/keys/keys.go buildArrowIterators1 CVEs · pkg/query/build_tree.go

All patched functions in authzed/spicedb

Frequently asked questions

Common questions about CVE fixes to ServiceTester.

How many CVEs have patched ServiceTester?: 1 published CVEs changed ServiceTester in authzed/spicedb, in 1 distinct patches totalling 2 changed lines, between 2024 and 2024.
What is the latest CVE that changed ServiceTester?: CVE-2024-48909 (SpiceDB calls to LookupResources using LookupResources2 with caveats may return context is missing when it is not), published 2024-10-14, changed lines 31 of internal/services/integrationtesting/consistencytestutil/servicetester.go.
How does ServiceTester compare to the rest of authzed/spicedb?: authzed/spicedb has 14 CVEs with a located fix in total; 1 of them changed ServiceTester.
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 authzed/spicedb 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