Discord account access via committed configuration token
Published Feb 20, 2024 · Updated Aug 28, 2024
Sensitive information exposure in Kedi ElectronCord allows remote attackers to obtain a Discord account token from a public commit. The affected commit stores the account access token in config.json within the public repository, allowing the credential to be retrieved without authorization. No authentication or user interaction is required; possession of the token grants the Discord account permissions associated with that credential.
Summary
What happened
Sensitive information exposure in Kedi ElectronCord allows remote attackers to obtain a Discord account token from a public commit. The affected commit stores the account access token in config.json within the public repository, allowing the credential to be retrieved without authorization. No authentication or user interaction is required; possession of the token grants the Discord account permissions associated with that credential.
The record
- CVE
- CVE-2024-26136
- Published
- Feb 20, 2024
- Updated
- Aug 28, 2024
- Vendor
- Kedi
- Product
- ElectronCord
- Classifications
- CWE-200, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=commit_aaaeaf4e6c99893827b2eea4dd02f755e1e24041
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo