CWE-532
AllowedInsertion of Sensitive Information into Log File
Abstraction: Base · Status: Incomplete
The product writes sensitive information to a log file.
1839 vulnerabilities reference this CWE, most recent first.
GHSA-269M-C36J-R834
Vulnerability from github – Published: 2025-01-28 09:32 – Updated: 2025-03-12 14:45A flaw was found in Infinispan, when using JGroups with JDBC_PING. This issue occurs when an application inadvertently exposes sensitive information, such as configuration details or credentials, through logging mechanisms. This exposure can lead to unauthorized access and exploitation by malicious actors.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.infinispan:infinispan-parent"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "15.1.4.Final"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-0736"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": true,
"github_reviewed_at": "2025-01-28T19:15:59Z",
"nvd_published_at": "2025-01-28T09:15:09Z",
"severity": "MODERATE"
},
"details": "A flaw was found in Infinispan, when using JGroups with JDBC_PING. This issue occurs when an application inadvertently exposes sensitive information, such as configuration details or credentials, through logging mechanisms. This exposure can lead to unauthorized access and exploitation by malicious actors.",
"id": "GHSA-269m-c36j-r834",
"modified": "2025-03-12T14:45:44Z",
"published": "2025-01-28T09:32:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0736"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2663"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2025-0736"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2342233"
},
{
"type": "PACKAGE",
"url": "https://github.com/infinispan/infinispan"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Infinispan vulnerable to Insertion of Sensitive Information into Log File"
}
GHSA-26F4-XFJH-462V
Vulnerability from github – Published: 2024-04-24 09:30 – Updated: 2026-04-01 18:31Insertion of Sensitive Information into Log File vulnerability in Patrick Posner Simply Static.This issue affects Simply Static: from n/a through 3.1.3.
{
"affected": [],
"aliases": [
"CVE-2024-32825"
],
"database_specific": {
"cwe_ids": [
"CWE-201",
"CWE-532"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-24T08:15:41Z",
"severity": "HIGH"
},
"details": "Insertion of Sensitive Information into Log File vulnerability in Patrick Posner Simply Static.This issue affects Simply Static: from n/a through 3.1.3.",
"id": "GHSA-26f4-xfjh-462v",
"modified": "2026-04-01T18:31:46Z",
"published": "2024-04-24T09:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-32825"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/simply-static/vulnerability/wordpress-simply-static-plugin-3-1-3-sensitive-data-exposure-via-log-file-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/simply-static/wordpress-simply-static-plugin-3-1-3-sensitive-data-exposure-via-log-file-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-26MW-3PV7-3GQF
Vulnerability from github – Published: 2022-11-02 19:00 – Updated: 2022-11-04 19:01An exposure of sensitive information to an unauthorized actor vulnerabiltiy [CWE-200] in FortiClient for Mac versions 7.0.0 through 7.0.5 may allow a local authenticated attacker to obtain the SSL-VPN password in cleartext via running a logstream for the FortiTray process in the terminal.
{
"affected": [],
"aliases": [
"CVE-2022-33878"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-11-02T12:15:00Z",
"severity": "MODERATE"
},
"details": "An exposure of sensitive information to an unauthorized actor vulnerabiltiy [CWE-200] in FortiClient for Mac versions 7.0.0 through 7.0.5 may allow a local authenticated attacker to obtain the SSL-VPN password in cleartext via running a logstream for the FortiTray process in the terminal.",
"id": "GHSA-26mw-3pv7-3gqf",
"modified": "2022-11-04T19:01:16Z",
"published": "2022-11-02T19:00:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-33878"
},
{
"type": "WEB",
"url": "https://fortiguard.com/psirt/FG-IR-22-246"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-26WC-MJPC-3F8M
Vulnerability from github – Published: 2024-07-02 21:32 – Updated: 2024-10-24 18:30Vulnerability in Realtek RtsPer driver for PCIe Card Reader (RtsPer.sys) before 10.0.22000.21355 and Realtek RtsUer driver for USB Card Reader (RtsUer.sys) before 10.0.22000.31274 leaks driver logs that contain addresses of kernel mode objects, weakening KASLR.
{
"affected": [],
"aliases": [
"CVE-2022-25477"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-07-02T19:15:11Z",
"severity": "MODERATE"
},
"details": "Vulnerability in Realtek RtsPer driver for PCIe Card Reader (RtsPer.sys) before 10.0.22000.21355 and Realtek RtsUer driver for USB Card Reader (RtsUer.sys) before 10.0.22000.31274 leaks driver logs that contain addresses of kernel mode objects, weakening KASLR.",
"id": "GHSA-26wc-mjpc-3f8m",
"modified": "2024-10-24T18:30:40Z",
"published": "2024-07-02T21:32:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-25477"
},
{
"type": "WEB",
"url": "https://gist.github.com/zwclose/feb16f1424779a61cb1d9f6d5681408a"
},
{
"type": "WEB",
"url": "https://www.realtek.com/images/safe-report/Realtek_RtsPer_RtsUer_Security_Advisory_Report.pdf"
},
{
"type": "WEB",
"url": "https://zwclose.github.io/2024/10/14/rtsper1.html"
},
{
"type": "WEB",
"url": "http://realtek.com"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-26WH-CC3R-W6PJ
Vulnerability from github – Published: 2025-04-02 22:36 – Updated: 2025-04-03 13:26Impact
Users using the github-token input are impacted.
If the get-workflow-version-action step fails, the exception output may include the GITHUB_TOKEN. If the full token is included in the exception output, GitHub will automatically redact the secret from the GitHub Actions logs. However, the token may be truncated—causing part of the GITHUB_TOKEN to be displayed in plaintext in the GitHub Actions logs.
Anyone with read access to the GitHub repository can view GitHub Actions logs. For public repositories, anyone can view the GitHub Actions logs.
The opportunity to exploit this vulnerability is limited—the GITHUB_TOKEN is automatically revoked when the job completes. However, there is an opportunity for an attack in the time between the GITHUB_TOKEN being displayed in the logs and the completion of the job. Normally this is less than a second, but it may be greater if continue-on-error is used in the get-workflow-version-action step or if status check functions are used in a later step in the same job. For an example of an attack in the time between the GITHUB_TOKEN being displayed in the logs & the completion of the job, see https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/
For users who passed the GITHUB_TOKEN to the github-token input, update to v1.0.1. Any secrets that were partially leaked while using v1.0.0 should have already been revoked, since the GITHUB_TOKEN is automatically revoked when the job completes. However, in the unlikely event that an attack was executed using a GITHUB_TOKEN before it was revoked (as described above), users' repositories may still be impacted—for example, a sophisticated attack could have used the GITHUB_TOKEN to push something to the repository.
The potential effects of an attack depend on the permissions of any GITHUB_TOKENs that were leaked. However, in a very sophisticated attack, even a GITHUB_TOKEN with read-only permissions can affect other GitHub Actions in the same repository if those actions use the Actions cache. For more information, see the "But Wait, There’s More" section of https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/ and https://github.com/AdnaneKhan/Cacheract
If any users used a long-lived secret (e.g. a personal access token) instead of the GITHUB_TOKEN in the github-token input, they should immediately revoke that secret. The get-workflow-version-action's documentation & examples all instructed the user to use the GITHUB_TOKEN, so it is unlikely that users used a long-lived secret instead of the GITHUB_TOKEN.
Patches
This has been fixed in v1.0.1. Also, the v1 tag has been updated to include the fix.
References
https://github.com/canonical/get-workflow-version-action/issues/2
{
"affected": [
{
"package": {
"ecosystem": "GitHub Actions",
"name": "canonical/get-workflow-version-action"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-31479"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": true,
"github_reviewed_at": "2025-04-02T22:36:03Z",
"nvd_published_at": "2025-04-02T22:15:20Z",
"severity": "HIGH"
},
"details": "### Impact\nUsers using the [`github-token` input](https://github.com/canonical/get-workflow-version-action/blob/a5d53b08d254a157ea441c9819ea5002ffc12edc/action.yaml#L10) are impacted.\n\nIf the `get-workflow-version-action` step fails, the exception output may include the GITHUB_TOKEN. If the full token is included in the exception output, GitHub will automatically redact the secret from the GitHub Actions logs. However, the token may be truncated\u2014causing part of the GITHUB_TOKEN to be displayed in plaintext in the GitHub Actions logs.\n\nAnyone with read access to the GitHub repository can view GitHub Actions logs. For public repositories, anyone can view the GitHub Actions logs.\n\nThe opportunity to exploit this vulnerability is limited\u2014the GITHUB_TOKEN is automatically revoked when the job completes. However, there is an opportunity for an attack in the time between the GITHUB_TOKEN being displayed in the logs and the completion of the job. Normally this is less than a second, but it may be greater if [`continue-on-error`](https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is used in the `get-workflow-version-action` step or if [status check functions](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#status-check-functions) are used in a later step in the same job. For an example of an attack in the time between the GITHUB_TOKEN being displayed in the logs \u0026 the completion of the job, see https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/\n\nFor users who passed the GITHUB_TOKEN to the `github-token` input, update to `v1.0.1`. Any secrets that were partially leaked while using `v1.0.0` should have already been revoked, since the GITHUB_TOKEN is automatically revoked when the job completes. However, in the unlikely event that an attack was executed using a GITHUB_TOKEN before it was revoked (as described above), users\u0027 repositories may still be impacted\u2014for example, a sophisticated attack could have used the GITHUB_TOKEN to push something to the repository.\n\nThe potential effects of an attack depend on the permissions of any GITHUB_TOKENs that were leaked. However, in a very sophisticated attack, even a GITHUB_TOKEN with read-only permissions can affect other GitHub Actions in the same repository if those actions use the Actions [cache](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows). For more information, see the \"But Wait, There\u2019s More\" section of https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/ and https://github.com/AdnaneKhan/Cacheract\n\nIf any users used a long-lived secret (e.g. a personal access token) instead of the GITHUB_TOKEN in the `github-token` input, they should immediately revoke that secret. The `get-workflow-version-action`\u0027s documentation \u0026 examples all instructed the user to use the GITHUB_TOKEN, so it is unlikely that users used a long-lived secret instead of the GITHUB_TOKEN.\n\n### Patches\nThis has been fixed in `v1.0.1`. Also, the `v1` tag has been updated to include the fix.\n\n### References\nhttps://github.com/canonical/get-workflow-version-action/issues/2",
"id": "GHSA-26wh-cc3r-w6pj",
"modified": "2025-04-03T13:26:02Z",
"published": "2025-04-02T22:36:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/canonical/get-workflow-version-action/security/advisories/GHSA-26wh-cc3r-w6pj"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31479"
},
{
"type": "WEB",
"url": "https://github.com/canonical/get-workflow-version-action/issues/2"
},
{
"type": "WEB",
"url": "https://github.com/canonical/get-workflow-version-action/commit/88281a62e96e1c0ef4df30352ae0668a9f3e3369"
},
{
"type": "PACKAGE",
"url": "https://github.com/canonical/get-workflow-version-action"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "canonical/get-workflow-version-action can leak a partial GITHUB_TOKEN in exception output"
}
GHSA-27Q6-3499-5X87
Vulnerability from github – Published: 2023-05-31 15:30 – Updated: 2024-04-04 04:25In JetBrains TeamCity before 2023.05 parameters of the "password" type from build dependencies could be logged in some cases
{
"affected": [],
"aliases": [
"CVE-2023-34223"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-05-31T14:15:10Z",
"severity": "MODERATE"
},
"details": "In JetBrains TeamCity before 2023.05 parameters of the \"password\" type from build dependencies could be logged in some cases",
"id": "GHSA-27q6-3499-5x87",
"modified": "2024-04-04T04:25:56Z",
"published": "2023-05-31T15:30:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-34223"
},
{
"type": "WEB",
"url": "https://www.jetbrains.com/privacy-security/issues-fixed"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-27R7-3M9X-R533
Vulnerability from github – Published: 2025-08-26 16:19 – Updated: 2025-08-29 21:03Impact
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.
{
"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"
}
GHSA-27RQ-4943-QCWP
Vulnerability from github – Published: 2022-04-28 00:00 – Updated: 2022-06-02 17:38The Hashicorp go-getter library before 1.5.11 could write SSH credentials into its logfile, exposing sensitive credentials to local users able to read the logfile.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/hashicorp/go-getter"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.5.11"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-29810"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": true,
"github_reviewed_at": "2022-05-03T20:19:26Z",
"nvd_published_at": "2022-04-27T06:15:00Z",
"severity": "MODERATE"
},
"details": "The Hashicorp go-getter library before 1.5.11 could write SSH credentials into its logfile, exposing sensitive credentials to local users able to read the logfile.",
"id": "GHSA-27rq-4943-qcwp",
"modified": "2022-06-02T17:38:26Z",
"published": "2022-04-28T00:00:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-29810"
},
{
"type": "WEB",
"url": "https://github.com/hashicorp/go-getter/pull/348"
},
{
"type": "WEB",
"url": "https://github.com/hashicorp/go-getter/commit/36b68b2f68a3ed10ee7ecbb0cb9f6b1dc5da49cc"
},
{
"type": "PACKAGE",
"url": "https://github.com/hashicorp/go-getter"
},
{
"type": "WEB",
"url": "https://github.com/hashicorp/go-getter/releases/tag/v1.5.11"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2022-0438"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Insertion of Sensitive Information into Log File in Hashicorp go-getter"
}
GHSA-27W6-8M77-X3QF
Vulnerability from github – Published: 2024-04-10 18:30 – Updated: 2025-04-08 18:34Insertion of Sensitive Information into Log File vulnerability in WebToffee WordPress Backup & Migration.This issue affects WordPress Backup & Migration: from n/a through 1.4.7.
{
"affected": [],
"aliases": [
"CVE-2024-31254"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-10T16:15:13Z",
"severity": "LOW"
},
"details": "Insertion of Sensitive Information into Log File vulnerability in WebToffee WordPress Backup \u0026 Migration.This issue affects WordPress Backup \u0026 Migration: from n/a through 1.4.7.",
"id": "GHSA-27w6-8m77-x3qf",
"modified": "2025-04-08T18:34:11Z",
"published": "2024-04-10T18:30:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-31254"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/wp-migration-duplicator/wordpress-wordpress-backup-migration-plugin-1-4-7-sensitive-data-exposure-via-log-file-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-2826-9VPV-CRX3
Vulnerability from github – Published: 2022-05-24 16:49 – Updated: 2023-03-01 18:31GitLab CE/EE, versions 8.0 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, would log access tokens in the Workhorse logs, permitting administrators with access to the logs to see another user's token.
{
"affected": [],
"aliases": [
"CVE-2018-19583"
],
"database_specific": {
"cwe_ids": [
"CWE-532"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-07-10T17:15:00Z",
"severity": "MODERATE"
},
"details": "GitLab CE/EE, versions 8.0 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, would log access tokens in the Workhorse logs, permitting administrators with access to the logs to see another user\u0027s token.",
"id": "GHSA-2826-9vpv-crx3",
"modified": "2023-03-01T18:31:02Z",
"published": "2022-05-24T16:49:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-19583"
},
{
"type": "WEB",
"url": "https://about.gitlab.com/2018/11/28/security-release-gitlab-11-dot-5-dot-1-released"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/gitlab-workhorse/issues/182"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/109166"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Mitigation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Mitigation
Remove debug log files before deploying the application into production.
Mitigation
Protect log files against unauthorized read/write.
Mitigation
Adjust configurations appropriately when software is transitioned from a debug state to production.
CAPEC-215: Fuzzing for application mapping
An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.