CVE-2024-28174
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 before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly
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 confidenceThe S3 Artifact Storage plugin in JetBrains TeamCity versions before 2023.11.4 had improper authorization logic when generating presigned URLs, potentially allowing unauthorized users to access artifacts stored in S3 buckets.
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< 2023.11.4CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/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.
-
Identify TeamCity installation versionAccess the TeamCity web UI and navigate to the Administration > About page, or use the TeamCity server API endpoint /app/rest/server to retrieve the server version informationAffected if The displayed version is lower than 2023.11.4 (e.g., 2023.11.3, 2023.11.2, earlier versions)
-
Confirm S3 Artifact Storage plugin is configuredNavigate to Administration > Artifacts Storage in the TeamCity web UI and check if an S3-compatible storage bucket is listed as a configured artifact storage pathAffected if S3 Artifact Storage is enabled and pointing to an S3 bucket (AWS S3, MinIO, or other S3-compatible storage)
-
Verify external artifact access methodReview project build configurations that expose artifacts externally or check if any build configurations have sharing settings enabled that allow artifact download via direct URLsAffected if Build artifacts are accessible via direct URL links that could potentially use presigned URLs for S3 bucket access
You are affected if your TeamCity version is below 2023.11.4 AND you have the S3 Artifact Storage plugin configured, as the improper authorization in presigned URL generation could allow unauthorized artifact access.
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 · scoped2023.11.4
Upgrade TeamCity to version 2023.11.4 or later to obtain the patched S3 Artifact Storage plugin with corrected presigned URL authorization checks.
2023.11.4
- Backup your TeamCity database and configuration files before proceeding with the upgrade
- Download TeamCity version 2023.11.4 or later from the official JetBrains website (www.jetbrains.com)
- Stop the running TeamCity server
- Follow the official TeamCity upgrade instructions to install the new version
- Start the TeamCity server and verify it runs successfully
- Confirm the S3 Artifact Storage plugin is functioning correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28174 — 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-2024-28174 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