kedi ElectronCord aaaeaf4e6c99893827b2eea4dd02f755e1e24041 on Discord Access Token config.json information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in kedi ElectronCord aaaeaf4e6c99893827b2eea4dd02f755e1e24041 on Discord. It has been declared as problematic. This impacts an unknown function of the file config.json of the component Access Token Handler. The manipulation results in information disclosure. This vulnerability is cataloged as CVE-2024-26136. The attack may be launched remotely. There is no exploit available. A patch should be applied to remediate this issue.
Details
A vulnerability was found in kedi ElectronCord aaaeaf4e6c99893827b2eea4dd02f755e1e24041 on Discord. It has been classified as problematic. Affected is some unknown processing of the file config.json of the component Access Token Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
kedi ElectronCord is a bot management tool for Discord. Commit aaaeaf4e6c99893827b2eea4dd02f755e1e24041 exposes an account access token in the `config.json` file. Malicious actors could potentially exploit this vulnerability to gain unauthorized access to sensitive information or perform malicious actions on behalf of the repository owner. As of time of publication, it is unknown whether the owner of the repository has rotated the token or taken other mitigation steps aside from informing users of the situation.
The weakness was shared 02/21/2024 as GHSA-ppwc-5vwp-mhw8. The advisory is available at github.com. This vulnerability is traded as CVE-2024-26136 since 02/14/2024. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
By approaching the search of inurl:config.json it is possible to find vulnerable targets with Google Hacking.
Applying the patch aaaeaf4e6c99893827b2eea4dd02f755e1e24041 is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: aaaeaf4e6c99893827b2eea4dd02f755e1e24041
Timeline
02/14/2024 🔍02/21/2024 🔍
02/21/2024 🔍
02/06/2025 🔍
Sources
Product: github.comAdvisory: GHSA-ppwc-5vwp-mhw8
Status: Confirmed
CVE: CVE-2024-26136 (🔍)
GCVE (CVE): GCVE-0-2024-26136
GCVE (VulDB): GCVE-100-254274
Entry
Created: 02/21/2024 07:31Updated: 02/06/2025 10:12
Changes: 02/21/2024 07:31 (54), 02/06/2025 10:12 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.