How many CVEs have patched respond_invalid?

1 published CVEs changed respond_invalid in getsentry/sentry, in 1 distinct patches totalling 25 changed lines, between 2022 and 2022.

What is the latest CVE that changed respond_invalid?

CVE-2022-23485 (Sentry vulnerable to invite code reuse via cookie manipulation), published 2022-12-10, changed lines 21 to 45 of src/sentry/api/endpoints/accept_organization_invite.py.

How does respond_invalid compare to the rest of getsentry/sentry?

getsentry/sentry has 19 CVEs with a located fix in total; 1 of them changed respond_invalid.

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

getsentry/sentry

Function

respond_invalid

Name: respond_invalid in getsentry/sentry: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/sentry/api/endpoints/accept_organization_invite.py

Last patched December 10, 2022

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

25

Lines changed

Added plus removed

2022

Years

By CVE publication date

Overview

respond_invalid in getsentry/sentry was changed by 1 published CVE fixes in 2022, in 1 distinct patches that added or removed 25 lines in total.

getsentry/sentry has 19 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

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

Sentry vulnerable to invite code reuse via cookie manipulation
CVE-2022-23485 · lines 21–45 · +15 −10
Medium · CVSS 6.4
EPSS 0.5%2022-12-10

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

Monitor sentry CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in getsentry/sentry changed by the most CVE fixes.

handle_unknown_identity2 CVEs · src/sentry/auth/helper.py dispatch1 CVEs · src/sentry/auth/providers/saml2/provider.py _validate_superuser1 CVEs · src/sentry/api/endpoints/auth_index.py strip_op_from_post1 CVEs · src/sentry/auth/providers/saml2/provider.py _login1 CVEs · src/sentry/auth/helper.py _build_confirmation_response1 CVEs · src/sentry/auth/helper.py

All patched functions in getsentry/sentry

Frequently asked questions

Common questions about CVE fixes to respond_invalid.

How many CVEs have patched respond_invalid?: 1 published CVEs changed respond_invalid in getsentry/sentry, in 1 distinct patches totalling 25 changed lines, between 2022 and 2022.
What is the latest CVE that changed respond_invalid?: CVE-2022-23485 (Sentry vulnerable to invite code reuse via cookie manipulation), published 2022-12-10, changed lines 21 to 45 of src/sentry/api/endpoints/accept_organization_invite.py.
How does respond_invalid compare to the rest of getsentry/sentry?: getsentry/sentry has 19 CVEs with a located fix in total; 1 of them changed respond_invalid.
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 getsentry/sentry 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