FKIE_CVE-2025-57732

Vulnerability from fkie_nvd - Published: 2025-08-20 10:15 - Updated: 2025-08-21 15:23
Severity ?
7.5 (High) - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
6.3 (Medium) - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Summary
In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership
References
cve@jetbrains.comhttps://www.jetbrains.com/privacy-security/issues-fixed/Vendor Advisory
Impacted products
Vendor Product Version
jetbrains teamcity *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:jetbrains:teamcity:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "86B4BDBF-76E7-45A7-B10F-B2A7C27EC067",
              "versionEndExcluding": "2025.07.1",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership"
    },
    {
      "lang": "es",
      "value": "En JetBrains TeamCity antes del 1/07/2025 la escalada de privilegios era posible debido a una propiedad incorrecta del directorio"
    }
  ],
  "id": "CVE-2025-57732",
  "lastModified": "2025-08-21T15:23:21.943",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.1,
        "impactScore": 5.8,
        "source": "cve@jetbrains.com",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 6.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.0,
        "impactScore": 5.2,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2025-08-20T10:15:31.173",
  "references": [
    {
      "source": "cve@jetbrains.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://www.jetbrains.com/privacy-security/issues-fixed/"
    }
  ],
  "sourceIdentifier": "cve@jetbrains.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-282"
        }
      ],
      "source": "cve@jetbrains.com",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.