CVE-2024-36589VulnerabilityPublished 13 Jun 2024Updated 25 Nov 2024

CVE-2024-36589: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-36589 effectively, organizations should: 1) Conduct a thorough code audit of the affected components (DecentralizeJustice/anonymousLocker and anonBackend) to identify all instances of plaintext credential storage. 2) Implement secure credential storage practices by encrypting credentials at rest using strong cryptographic algorithms or leveraging secure vault solutions such as HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault. 3) Replace plaintext storage with hashed credentials where applicable, using salted cryptographic hashes for passwords or sensitive tokens. 4) Restrict access to credential storage locations using strict access controls and least privilege principles to minimize exposure risk. 5) Monitor logs and access patterns for suspicious activity that may indicate attempts to access stored credentials. 6) Stay updated with vendor or community patches addressing this vulnerability and apply them promptly once available. 7) Educate developers and administrators on secure coding and credential management best practices to prevent recurrence. 8) If immediate patching is not feasible, consider isolating affected components within segmented network zones to reduce attack surface exposure. These steps go beyond generic advice by focusing on secure storage implementation, access control, and proactive monitoring tailored to the specific vulnerability context.

Description

An issue in Annonshop.app DecentralizeJustice/anonymousLocker commit 2b2b4 to ba9fd and DecentralizeJustice/anonBackend commit 57837 to cd815 was discovered to store credentials in plaintext.

Impact

The primary impact of CVE-2024-36589 is the potential disclosure of sensitive credentials due to their storage in plaintext. This compromises confidentiality, allowing attackers who gain access to the storage location or source code to retrieve authentication data easily. Such exposure can lead to unauthorized access to systems, data breaches, and further exploitation within the affected environment. Since the vulnerability does not affect integrity or availability, the direct impact is limited to credential confidentiality. However, compromised credentials can enable attackers to escalate privileges, move laterally, or access sensitive resources, amplifying the overall risk. Organizations using the affected components in decentralized applications or backend services may face increased risk of account compromise, data leakage, and erosion of trust in their security posture. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often target plaintext credential storage. The medium severity rating suggests that while the vulnerability is not critical, it warrants timely attention to prevent potential exploitation.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/go-compile/security-advisories/blob/master/vulns/CVE-2024-36589.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 05:06 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats