ghsa-w796-2gq9-7jm8
Vulnerability from github
Published
2023-09-19 18:30
Modified
2024-12-16 12:30
Severity ?
Details

In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2023-42793",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-288",
         "CWE-306",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2023-09-19T17:15:08Z",
      severity: "CRITICAL",
   },
   details: "In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible",
   id: "GHSA-w796-2gq9-7jm8",
   modified: "2024-12-16T12:30:29Z",
   published: "2023-09-19T18:30:16Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2023-42793",
      },
      {
         type: "WEB",
         url: "https://attackerkb.com/topics/1XEEEkGHzt/cve-2023-42793",
      },
      {
         type: "WEB",
         url: "https://blog.jetbrains.com/teamcity/2023/09/cve-2023-42793-vulnerability-post-mortem",
      },
      {
         type: "WEB",
         url: "https://www.jetbrains.com/privacy-security/issues-fixed",
      },
      {
         type: "WEB",
         url: "https://www.rapid7.com/blog/post/2023/09/25/etr-cve-2023-42793-critical-authentication-bypass-in-jetbrains-teamcity-ci-cd-servers",
      },
      {
         type: "WEB",
         url: "https://www.securityweek.com/recently-patched-teamcity-vulnerability-exploited-to-hack-servers",
      },
      {
         type: "WEB",
         url: "https://www.sonarsource.com/blog/teamcity-vulnerability",
      },
      {
         type: "WEB",
         url: "http://packetstormsecurity.com/files/174860/JetBrains-TeamCity-Unauthenticated-Remote-Code-Execution.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.