Ditty – Responsive News Tickers, Sliders, and…: Deserialization of Untrusted Data
CVE-2024-3954 is a high-severity deserialization of untrusted data vulnerability in Ditty – Responsive News Tickers, Sliders, and Lists from Metaphorcreations, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Ditty – Responsive News Tickers, Sliders, and Lists versions: 3.1.38 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.66% chance of exploitation within 30 days, higher than 52% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Ditty – Responsive News Tickers, Sliders, and Lists you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Metaphorcreations | Ditty – Responsive News Tickers, Sliders, and Lists | 3.1.38 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (wordfence.com).
Official description
The Ditty plugin for WordPress is vulnerable to PHP Object Injection in all versions up to 3.1.38 via deserialization of untrusted input when adding a new ditty. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Ditty – Responsive News Tickers, Sliders, and Lists
- 7.5 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 7.2 High severity
- 9.9 Critical severity
Spotted an error? Tell us.