dbcve.org
HubApplication · Jetbrains

CVE-2022-45471

HIGH · 7.5 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 2022.3.15181 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In JetBrains Hub before 2022.3.15181 Throttling was missed when sending emails to a particular email address

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In JetBrains Hub before version 2022.3.15181, throttling (rate limiting) was not enforced when sending emails to a particular email address. This missing throttling could allow an attacker or automated process to send unlimited emails to a specific recipient, potentially leading to email abuse, spam distribution, or resource exhaustion on the mail server.

MitigationUpgrade JetBrains Hub to version 2022.3.15181 or later to obtain the throttling fix. Alternatively, implement rate limiting on the email sending functionality at the application or mail server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HubApplication
Affected:< 2022.3.15181

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm JetBrains Hub is installed
    Check if Hub is running in your environment by accessing the Hub administration interface or checking running processes for Hub-related Java applications
    Affected if JetBrains Hub is not installed in your environment, this CVE does not apply
  2. Locate the installed Hub version
    Access the Hub administration interface (typically at /hub/admin) and navigate to the About or Version section, or check startup logs for version information
    Affected if You cannot determine the version, further investigation is required
  3. Compare your version to the affected range
    Verify the installed version against the affected range: versions prior to 2022.3.15181 are vulnerable. If your version starts with 2022.3 and the build number is below 15181, or if it is an earlier major version, you are affected
    Affected if Your installed version is 2022.3.x where x is less than 15181, or your version is any release prior to 2022.3
  4. Verify email sending is enabled
    Check Hub configuration to confirm email notification features are enabled in the notification settings or mail server integration settings
    Affected if Email sending is disabled in your Hub instance, the specific abuse vector is not reachable though the underlying configuration gap still exists

You are affected if JetBrains Hub is installed with a version lower than 2022.3.15181 and email notifications are enabled, allowing unlimited emails to a specific recipient without rate limiting.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2022.3.15181 or later
Fixed in 2022.3.15181
Interim mitigation

Upgrade JetBrains Hub to version 2022.3.15181 or later to obtain the throttling fix. Alternatively, implement rate limiting on the email sending functionality at the application or mail server level.

Recommended fix High confidence

2022.3.15181

  1. Back up your Hub installation and database before upgrading
  2. Stop the Hub service
  3. Download JetBrains Hub version 2022.3.15181 or later from the official JetBrains website
  4. Install the upgrade following JetBrains standard upgrade procedures
  5. Start the Hub service and verify the upgrade was successful

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45471 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45471 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data