A vulnerability, which was classified as critical, was found in Kirby up to 3.5.8.2/3.6.6.2/3.7.5.1/3.8.4.0/3.9.5. Affected is an unknown function. The manipulation with an unknown input leads to a improper neutralization of delimiters vulnerability. CWE is classifying the issue as CWE-140. The product does not neutralize or incorrectly neutralizes delimiters. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Kirby is a content management system. A vulnerability in versions prior to 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6 affects all Kirby sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update a Kirby content file (e.g. via a contact or comment form). Kirby sites are *not* affected if they don't allow write access for untrusted users or visitors. A field injection in a content storage implementation is a type of vulnerability that allows attackers with content write access to overwrite content fields that the site developer didn't intend to be modified. In a Kirby site this can be used to alter site content, break site behavior or inject malicious data or code. The exact security risk depends on the field type and usage. Kirby stores content of the site, of pages, files and users in text files by default. The text files use Kirby's KirbyData format where each field is separated by newlines and a line with four dashes (`----`). When reading a KirbyData file, the affected code first removed the Unicode BOM sequence from the file contents and afterwards split the content into fields by the field separator. When writing to a KirbyData file, field separators in field data are escaped to prevent user input from interfering with the field structure. However this escaping could be tricked by including a Unicode BOM sequence in a field separator (e.g. `--\xEF\xBB\xBF--`). When writing, this was not detected as a separator, but because the BOM was removed during reading, it could be abused by attackers to inject other field data into content files. Because each field can only be defined once per content file, this vulnerability only affects fields in the content file that were defined above the vulnerable user-writable field or not at all. Fields that are defined below the vulnerable field override the injected field content and were therefore already protected. The problem has been patched in Kirby 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and Kirby 3.9.6. In all of the mentioned releases, the maintainers have fixed the affected code to only remove the Unicode BOM sequence at the beginning of the file. This fixes this vulnerability both for newly written as well as for existing content files.

The weakness was presented 07/27/2023 as GHSA-x5mr-p6v4-wp93. The advisory is available at github.com. This vulnerability is traded as CVE-2023-38488 since 07/18/2023. The technical details are unknown and an exploit is not available.

Upgrading to version 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1 or 3.9.6 eliminates this vulnerability. Applying the patch a1e0f81c799ddae1af91cf37216f8ded9cb93540 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Productinfo

Name

• Kirby

Version

• 3.5.8.0
• 3.5.8.1
• 3.5.8.2
• 3.6.6.0
• 3.6.6.1
• 3.6.6.2
• 3.7.5.0
• 3.7.5.1
• 3.8.0
• 3.8.1
• 3.8.2
• 3.8.3
• 3.8.4
• 3.9.0
• 3.9.1
• 3.9.2
• 3.9.3
• 3.9.4
• 3.9.5

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion