CVE-2024-39879
First published: Mon Jul 01 2024(Updated: )
In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings
Credit: cve@jetbrains.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| JetBrains TeamCity | <2024.03.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-39879?
CVE-2024-39879 is classified as a high-severity vulnerability due to the potential exposure of application tokens.
How do I fix CVE-2024-39879?
To fix CVE-2024-39879, upgrade JetBrains TeamCity to version 2024.03.3 or later.
What impact does CVE-2024-39879 have on JetBrains TeamCity?
CVE-2024-39879 allows unauthorized access to sensitive application tokens in EC2 Cloud Profile settings.
Is CVE-2024-39879 present in older versions of TeamCity?
Yes, CVE-2024-39879 affects all versions of JetBrains TeamCity prior to 2024.03.3.
Can CVE-2024-39879 lead to further security issues?
Yes, the exposure of application tokens in CVE-2024-39879 could lead to unauthorized access and potential data breaches.
- agent/weakness
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/jetbrains
- canonical/jetbrains teamcity