CVE-2022-46830
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 TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning.
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 confidenceA custom STS endpoint in JetBrains TeamCity versions 2022.10 through 2022.10.1 contained a vulnerability that allowed internal port scanning, potentially exposing internal network infrastructure details to remote attackers.
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.10, <= 2022.10.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Check installed TeamCity versionAccess the TeamCity administration interface and navigate to the 'About' page, or use the command-line tool if available, to retrieve the exact version numberAffected if The installed version is 2022.10 or 2022.10.1
-
Compare the installed version against the vulnerable range: versions 2022.10 through 2022.10.1 (inclusive)Affected if Version is >= 2022.10 and <= 2022.10.1
-
Review TeamCity server configuration and exposed web endpoints for a custom STS (Security Token Service) endpoint that handles authentication requestsAffected if A custom STS endpoint exists and is accessible on the server
-
Attempt to access the STS endpoint from an external network perspective or review server access logs to confirm the endpoint accepts external requestsAffected if The STS endpoint is reachable from untrusted network segments
You are affected if your TeamCity installation is version 2022.10 or 2022.10.1 and the custom STS endpoint is network-accessible, allowing potential internal port scanning by remote attackers.
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 · scopedUpgrade TeamCity to version 2022.10.2 or later to address the vulnerable STS endpoint; verify the upgrade in a staging environment first.
TeamCity 2022.10.2 or later
- 1. Back up your TeamCity data directory and database before upgrading.
- 2. Download TeamCity 2022.10.2 or later from the official JetBrains website.
- 3. Stop the TeamCity server.
- 4. Install the new version following the standard upgrade procedure.
- 5. Start the TeamCity server and verify all services are running correctly.
- 6. Review server logs for any errors following the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46830 — 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-46830 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