CVE-2025-58401
BaseFortify
Publication date: 2025-09-05
Last updated on: 2025-09-05
Assigner: JPCERT/CC
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pierrad | obsidian-github-copilot | 1.1.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-312 | The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Obsidian GitHub Copilot Plugin versions prior to 1.1.7, where the GitHub API token is stored in cleartext without encryption. This means an attacker with local access can obtain the token and use it to perform unauthorized operations on the linked GitHub account. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability allows an attacker with local access to steal the GitHub API token and perform unauthorized actions on your GitHub account, potentially leading to data exposure, code manipulation, or other malicious activities within your repositories. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the Obsidian GitHub Copilot Plugin version installed is prior to 1.1.7, as those versions store the GitHub API token in cleartext. Additionally, you can search for the presence of cleartext GitHub API tokens in the plugin's configuration or storage files on the local system. For example, you can use commands like `grep -r 'ghp_' ~/.obsidian/plugins/github-copilot/` to search for GitHub tokens in plugin directories. Verifying the plugin version can be done by checking the plugin's manifest or version file. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Obsidian GitHub Copilot Plugin to version 1.1.7 or later, where the vulnerability has been fixed. This update ensures that the GitHub API token is no longer stored in cleartext, preventing unauthorized access. Additionally, if you suspect token exposure, you should revoke the compromised GitHub API token and generate a new one. [1]