CVE-2022-46829
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 · uneditedIn JetBrains JetBrains Gateway before 2022.3 a client could connect without a valid token if the host consented.
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 · high confidenceIn JetBrains JetBrains Gateway before version 2022.3, a client could connect to the Gateway server without presenting a valid authentication token. The vulnerability required the host machine to have explicitly consented to this behavior, which could be enabled through certain configuration settings.
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< 2022.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify JetBrains Gateway is installedCheck for JetBrains Gateway application in your system. On Windows, look in Program Files or the JetBrains toolbox. On macOS, check /Applications. On Linux, check /opt or ~/.Affected if JetBrains Gateway is present on the system
-
Determine installed Gateway versionOpen JetBrains Gateway and navigate to Help > About, or check the version displayed in the application startup window. Compare the version number to 2022.3.Affected if Version is earlier than 2022.3
-
Inspect Gateway authentication settingsAccess JetBrains Gateway configuration files or settings panel. Look for options related to authentication, token requirements, or remote access permissions. The CVE specifically mentions 'host consent' settings that must be explicitly enabled for this vulnerability to apply.Affected if Configuration allows connections without valid authentication token and host consent was explicitly granted
-
Review remote access configurationCheck JetBrains Gateway connection settings for any options that disable or bypass token authentication. The vulnerability required the host to manually enable a setting that permitted unauthenticated connections.Affected if Remote access is configured to allow connections without presenting a valid authentication token
You are affected if JetBrains Gateway version is earlier than 2022.3 AND the host has explicitly enabled a configuration setting that allows unauthenticated remote connections.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.3
Upgrade JetBrains Gateway to version 2022.3 or later. Alternatively, audit host consent settings to ensure no unauthorized remote access configurations are enabled.
JetBrains Gateway 2022.3 or later
- 1. Open JetBrains Gateway
- 2. Navigate to Help > Check for Updates
- 3. If an update to version 2022.3 or later is available, apply the update
- 4. Restart the application after the update completes
- 5. Verify the update was successful by checking the version number in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-46829 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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