CVE-2025-57813

traQ is a messenger application built for Digital Creators Club traP. Prior to version 3.25.0, a vulnerability exists where sensitive information, such as OAuth tokens, are 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. This vulnerability has been patched in version 3.25.0. If upgrading is not possible, a temporary workaround involves reviewing access permissions for SQL error logs and strictly limiting access to prevent unauthorized users from viewing them.

CVSS v3 5.9 MEDIUM

5.9^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 0.7 / Impact : 5.2

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://github.com/traPtitech/traQ/commit/ce5da94f5d5a8348f9ecdc82140b6f53b3721698
https://github.com/traPtitech/traQ/pull/2787
https://github.com/traPtitech/traQ/security/advisories/GHSA-27r7-3m9x-r533

Configurations

No configuration.

History

No history.

Information

Published : 2025-08-26 16:15

Updated : 2025-08-29 16:22

NVD link : CVE-2025-57813

Mitre link : CVE-2025-57813

CVE.ORG link : CVE-2025-57813

JSON object : View

Products Affected

No product.

CWE

CWE-532

Insertion of Sensitive Information into Log File

{"id": "CVE-2025-57813", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "[email protected]", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 0.7}]}, "published": "2025-08-26T16:15:38.040", "references": [{"url": "https://github.com/traPtitech/traQ/commit/ce5da94f5d5a8348f9ecdc82140b6f53b3721698", "source": "[email protected]"}, {"url": "https://github.com/traPtitech/traQ/pull/2787", "source": "[email protected]"}, {"url": "https://github.com/traPtitech/traQ/security/advisories/GHSA-27r7-3m9x-r533", "source": "[email protected]"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-532"}]}], "descriptions": [{"lang": "en", "value": "traQ is a messenger application built for Digital Creators Club traP. Prior to version 3.25.0, a vulnerability exists where sensitive information, such as OAuth tokens, are 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. This vulnerability has been patched in version 3.25.0. If upgrading is not possible, a temporary workaround involves reviewing access permissions for SQL error logs and strictly limiting access to prevent unauthorized users from viewing them."}, {"lang": "es", "value": "traQ es una aplicaci\u00f3n de mensajer\u00eda desarrollada para Digital Creators Club traP. Antes de la versi\u00f3n 3.25.0, exist\u00eda una vulnerabilidad que permit\u00eda registrar informaci\u00f3n confidencial, como tokens OAuth, en archivos de registro cuando se produc\u00eda un error durante la ejecuci\u00f3n de una consulta SQL. Un atacante podr\u00eda generar intencionalmente un error SQL mediante m\u00e9todos como sobrecargar la base de datos. Esto podr\u00eda permitir que un atacante con autorizaci\u00f3n para ver los archivos de registro adquiera il\u00edcitamente la informaci\u00f3n confidencial registrada. Esta vulnerabilidad se ha corregido en la versi\u00f3n 3.25.0. Si no es posible actualizar, una soluci\u00f3n temporal consiste en revisar los permisos de acceso a los registros de errores SQL y limitar estrictamente el acceso para evitar que usuarios no autorizados los vean."}], "lastModified": "2025-08-29T16:22:31.970", "sourceIdentifier": "[email protected]"}