GHSA-27R7-3M9X-R533

Vulnerability from github – Published: 2025-08-26 16:19 – Updated: 2025-08-29 21:03
VLAI
Summary
traQ Allows Insertion of Sensitive Information into Log File
Details

Impact

A vulnerability exists where sensitive information, such as OAuth tokens, is recorded in log files when an error occurs during the execution of an SQL query. An attacker could intentionally trigger an SQL error by methods such as placing a high load on the database. This could allow an attacker who has the authority to view the log files to illicitly acquire the recorded sensitive information.

Patch

This vulnerability was temporarily fixed by #2787 and will be completely resolved by #2788.

This issue may have caused OAuth tokens to be leaked to users who can view logs on traQ instances using versions prior to v3.25.0.

While it is possible that OAuth tokens for both human users and Bots were leaked, revoking Bot access tokens is not recommended as it may cause errors. This issue will be resolved in a future update.

Currently, the recommended mitigation is to invalidate the OAuth tokens of human users only. To apply this measure, please execute the following SQL statement directly:

UPDATE oauth2_tokens SET deleted_at = NOW() WHERE deleted_at IS NULL AND scopes != "bot"

Workaround

If you cannot apply the update immediately, as a temporary workaround, please review access permissions for SQL error logs and strictly limit access to prevent unauthorized users from viewing them.

Severity
5.9 (Medium)
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/traPtitech/traQ"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.25.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-57813"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-532"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-08-26T16:19:41Z",
    "nvd_published_at": "2025-08-26T16:15:38Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nA vulnerability exists where sensitive information, such as OAuth tokens, is recorded in log files when an error occurs during the execution of an SQL query.\nAn attacker could intentionally trigger an SQL error by methods such as placing a high load on the database. This could allow an attacker who has the authority to view the log files to illicitly acquire the recorded sensitive information.\n\n### Patch\nThis vulnerability was temporarily fixed by #2787 and will be completely resolved by #2788. \n\nThis issue may have caused OAuth tokens to be leaked to users who can view logs on traQ instances using versions prior to v3.25.0.\n\nWhile it is possible that OAuth tokens for both human users and Bots were leaked, revoking Bot access tokens is not recommended as it may cause errors. This issue will be resolved in a future update.\n\nCurrently, the recommended mitigation is to invalidate the OAuth tokens of human users only. To apply this measure, please execute the following SQL statement directly:\n```sql\nUPDATE oauth2_tokens SET deleted_at = NOW() WHERE deleted_at IS NULL AND scopes != \"bot\"\n```\n\n### Workaround\nIf you cannot apply the update immediately, as a temporary workaround, please review access permissions for SQL error logs and strictly limit access to prevent unauthorized users from viewing them.",
  "id": "GHSA-27r7-3m9x-r533",
  "modified": "2025-08-29T21:03:36Z",
  "published": "2025-08-26T16:19:41Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/security/advisories/GHSA-27r7-3m9x-r533"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-57813"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/pull/2787"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/pull/2788"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/commit/ce5da94f5d5a8348f9ecdc82140b6f53b3721698"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/traPtitech/traQ"
    },
    {
      "type": "WEB",
      "url": "https://pkg.go.dev/vuln/GO-2025-3913"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "traQ Allows Insertion of Sensitive Information into Log File"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.