Skip to main content
VulnerabilityPublished Updated

CVE-2024-29672: reden-is-what-we-made · Directory Traversal

Affects reden-is-what-we-madeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 0.2.514 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.2.514
CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade zly2006/reden-is-what-we-made to 0.2.514.

Affected software

ProductAffectedFixed in
GitHubzly2006/reden-is-what-we-madepkg:github/zly2006/reden-is-what-we-madeOther threatsAffected
  • <0.2.514
Fixed in
  • 0.2.514

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade to Reden version 0.2.514 or later as soon as the patch is officially released to address the vulnerability. 2. If you cannot patch yet, restrict network access to the vulnerable DEBUG_RTC_REQUEST_SYNC_DATA interface by implementing firewall rules or network segmentation to limit exposure. 3. Monitor logs and network traffic for unusual requests targeting the KeyCallbacks.kt functionality or suspicious directory traversal patterns. 4. Employ application-layer filtering or web application firewalls (WAFs) that can detect and block directory traversal attempts. 5. Educate users about the risks of interacting with untrusted inputs or triggering unknown requests that may invoke vulnerable functions. 6. Conduct regular security assessments and code reviews focusing on input validation and path handling to prevent similar vulnerabilities. 7. Implement strict input validation and sanitization in development practices to avoid CWE-22 issues in future software versions. 8. Prepare incident response plans to quickly contain and remediate any exploitation attempts.

Description

Directory Traversal vulnerability in zly2006 Reden before v.0.2.514 allows a remote attacker to execute arbitrary code via the DEBUG_RTC_REQUEST_SYNC_DATA in KeyCallbacks.kt.

References

Community reviews

Loading reviews…