CVE-2023-29479VulnerabilityPublished 24 Apr 2023Updated 21 Nov 2025

CVE-2023-29479: n/a

Source CVE Database V5

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, 08:11 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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Apr 2023
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

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.

Impact

For European organizations, the primary impact of CVE-2023-29479 is the potential disruption of services relying on Ribose RNP for cryptographic operations such as encryption, decryption, and signing. This could affect secure communications, email encryption, software package signing, and other security-critical workflows. Denial-of-service conditions may lead to temporary unavailability of these services, impacting business continuity and operational efficiency. Organizations in sectors such as finance, government, healthcare, and critical infrastructure that depend on secure messaging and data protection could experience interruptions. While the vulnerability does not expose sensitive data or allow unauthorized access, the loss of availability can degrade trust in security systems and potentially delay critical operations. Additionally, if attackers combine this DoS with other attack vectors, it could facilitate broader disruption. Given the remote exploitability without authentication, attackers could target exposed services or interfaces that process OpenPGP data. The lack of known exploits reduces immediate risk, but proactive mitigation is essential to prevent future exploitation.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 21 Nov 2025, 20:14 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats