Skip to main content
VulnerabilityPublished Updated

CVE-2023-29479: Ribose RNP · Unthrottled Resource Allocation

Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium · fixed in 0.16.3 : update affected systems when convenient.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2023

  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

AI-suggested

  1. Upgrade Ribose RNP to version 0.16.3 or later as soon as the patch is available to ensure the vulnerability is addressed.
  2. Implement strict input validation and sanitization on all data processed by Ribose RNP or dependent applications to detect and reject malformed inputs before processing.
  3. Employ resource limiting and timeout mechanisms to prevent the software from hanging indefinitely when encountering unexpected input.
  4. Monitor logs and network traffic for unusual patterns indicative of malformed OpenPGP packets or repeated attempts to trigger the hang condition.
  5. Isolate critical cryptographic services behind firewalls and restrict access to trusted sources to reduce exposure to remote attacks.
  6. Conduct regular security assessments and fuzz testing on cryptographic components to identify and remediate similar resource exhaustion issues.
  7. Maintain an incident response plan that includes procedures for handling denial-of-service conditions affecting cryptographic services.
  8. Engage with Ribose RNP maintainers and community to stay informed about patches, advisories, and best practices.

Description

Ribose RNP before 0.16.3 may hang when the input is malformed.

References

Community reviews

Loading reviews…