CVE-2024-43372

✕ Withdrawn — historical dataHIGHCVSS · not yet scored
—

Persistent Cross-site Scripting in eZ Platform Rich Text Field Type

Impact

The validator for the RichText fieldtype blocklists javascript: and vbscript: in links to prevent XSS. This can leave other options open, and the check can be circumvented using upper case. Content editing permissions for RichText content is required to exploit this vulnerability, which typically means Editor role or higher. The fix implements an allowlist instead, which allows only approved link protocols. The new check is case insensitive.

Patches

  • See "Patched versions".
  • https://github.com/ezsystems/ezplatform-richtext/commit/6131975108fa9756e17043e7a06a4e72f786f842 (and follow-ups https://github.com/ezsystems/ezplatform-richtext/commit/8b75c603dfd1ad6f6f3db15ae2324876683cbaf9 and https://github.com/ezsystems/ezplatform-richtext/commit/7bbc6d024c6146d1e1ba84d27a3ebffe9459613e and https://github.com/ezsystems/ezplatform-richtext/commit/2c652915625c47b493a2be06924f4c87d1df7d8e and https://github.com/ezsystems/ezplatform-richtext/commit/dbe816f3ff4c903cc508dfdcdca8791c8284d292)

Workarounds

None.

References

  • Same issue in v4.6: https://github.com/ibexa/fieldtype-richtext/security/advisories/GHSA-hvcf-6324-cjh7
  • Ibexa advisory: https://developers.ibexa.co/security-advisories/ibexa-sa-2024-005-persistent-xss-in-richtext

Credit

This vulnerability was discovered and reported to Ibexa by Alec Romano: https://github.com/4rdr We thank them for reporting it responsibly to us.

How to report security issues: https://doc.ibexa.co/en/latest/infrastructure_and_maintenance/security/reporting_issues/

CVSS
—
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EPSS PROB
—
EPSS %ILE
—
KEV
—Not applicable: this CVE ID was withdrawn

Published

August 14, 2024

Last Modified

August 14, 2024

Frequently asked(3)

What is CVE-2024-43372?
CVE-2024-43372 is a rejected CVE ID: its record was withdrawn on August 19, 2024 and no longer describes a vulnerability. Reason given: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-43369. Reason: This candidate is a duplicate of CVE-2024-43369. Notes: All CVE users should reference CVE-2024-43369 instead of this candidate. This CVE was issued to a vulnerability that is dependent on CVE-2024-43369. According to rule 4.2.15 of the CVE CNA rules, "CNAs MUST NOT assign a different CVE ID to a Vulnerability that is fully interdependent with another Vulnerability. The Vulnerabilities are effectively the same si… Its record names CVE-2024-43369 as the replacement.
When was the CVE record for CVE-2024-43372 published?
The CVE record for CVE-2024-43372 was published on August 14, 2024. EchelonGraph's copy of the record carries a last-modified date of August 14, 2024; the record at its source may have been updated since.
How do I remediate CVE-2024-43372?
There is nothing to remediate under CVE-2024-43372: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability. Its record names CVE-2024-43369 as the replacement; act on that CVE instead.