Summary
With a known valid invite link (i.e. not already accepted or expired) an unauthenticated attacker can manipulate the cookie to allow the same invite link to be reused on multiple accounts when joining an organization.
Workarounds
Sentry SaaS customers do not need to take action.
Self-hosted Sentry installs can disable the invite functionality until they are ready to deploy the patched version by editing their sentry.conf.py file (usually located at ~/.sentry/).
Add the following line into
sentry.conf.py:SENTRY_FEATURES["organizations:invite-members"] = FalseRestart the Sentry web service.
docker compose restart web
For more information
If you have any questions or comments about this advisory:
- Visit our FAQs on this CVE
- Open an issue in getsentry/sentry
- Email us at security[@]sentry.io
Impact
An attacker with a valid invite link can create multiple users and join the organization from which the invite link was generated.
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
CVE-2022-23485 has a CVSS score of 6.4 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (22.11.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
This issue was patched in version 22.11.0.
Frequently Asked Questions
- What is CVE-2022-23485? CVE-2022-23485 is a medium-severity improper privilege management vulnerability in sentry (pip), affecting versions >= 20.6.0, < 22.11.0. It is fixed in 22.11.0. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- How severe is CVE-2022-23485? CVE-2022-23485 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of sentry are affected by CVE-2022-23485? sentry (pip) versions >= 20.6.0, < 22.11.0 is affected.
- Is there a fix for CVE-2022-23485? Yes. CVE-2022-23485 is fixed in 22.11.0. Upgrade to this version or later.
- Is CVE-2022-23485 exploitable, and should I be worried? Whether CVE-2022-23485 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-23485 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-23485? Upgrade
sentryto 22.11.0 or later.