A vulnerability, which was classified as problematic, has been found in Shirasagi up to 1.17.x. This issue affects some unknown functionality of the component Unicode Character Handler. The manipulation with an unknown input leads to a improper handling of unicode encoding vulnerability. Using CWE to declare the problem leads to CWE-176. The product does not properly handle when an input contains Unicode encoding. Impacted is integrity. The summary by CVE is:

SHIRASAGI is a Content Management System. Prior to version 1.18.0, SHIRASAGI is vulnerable to a Post-Unicode normalization issue. This happens when a logical validation or a security check is performed before a Unicode normalization. The Unicode character equivalent of a character would resurface after the normalization. The fix is initially performing the Unicode normalization and then strip for all whitespaces and then checking for a blank string. This issue has been fixed in version 1.18.0.

The weakness was presented 09/16/2023 as GHSA-xr45-c2jv-2v9r. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-41889 since 09/04/2023. Technical details are unknown but a public exploit is available.

The exploit is available at github.com. It is declared as proof-of-concept.

Upgrading to version 1.18.0 eliminates this vulnerability.

See VDB-17424, VDB-19898, VDB-49122 and VDB-102503 for similar entries.

Productinfo

Name

• Shirasagi

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion