# CVE-2024-28864: [TagAwareCipher] - Decryption Failure (Regex Match)

> Attackers can retrieve plaintext data from encrypted fields when using TagAwareCipher with NullEncoder due to regex failure, exposing sensitive information.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rj29-j2g4-77q8

## What is CVE-2024-28864?

CVE-2024-28864 is a low-severity vulnerability in IlicMiljan Secure-Props, published on 18 Mar 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SecureProps is a PHP library designed to simplify the encryption and decryption of property data in objects. A vulnerability in SecureProps version 1.2.0 and 1.2.1 involves a regex failing to detect tags during decryption of encrypted data. This occurs when the encrypted data has been encoded with `NullEncoder` and passed to `TagAwareCipher`, and contains special characters such as `\n`. As a result, the decryption process is skipped since the tags are not detected. This causes the encrypted data to be returned in plain format.  The vulnerability affects users who implement `TagAwareCipher` with any base cipher that has `NullEncoder` (not default). The patch for the issue has been released. Users are advised to update to version 1.2.2. As a workaround, one may use the default `Base64Encoder` with the base cipher decorated with `TagAwareCipher` to prevent special characters in the encrypted string from interfering with regex tag detection logic.  This workaround is safe but may involve double encoding since `TagAwareCipher` uses `NullEncoder` by default.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2024-28864?

2 open source packages ship an affected version, including ilicmiljan/secure-props. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ilicmiljan/secure-props` | Packagist | From 1.2.0 | 1.2.2 |
| `ilicmiljan/secure-props` | Packagist | From 1.2.0 | 1.2.2 |

Products: Ilicmiljan Secureprops.

## How do I fix CVE-2024-28864?

Upgrade ilicmiljan/secure-props to 1.2.2 or later.

## Is CVE-2024-28864 being exploited?

There is no known exploitation of CVE-2024-28864 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28864 and fix it if it is affected.

What it is: CVE-2024-28864 is a low-severity vulnerability in IlicMiljan Secure-Props, published on 18 Mar 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-28864 in the wild and no public exploit code.

Affected packages and fixed versions:
- ilicmiljan/secure-props (Packagist): affected from 1.2.0; fixed in 1.2.2
- ilicmiljan/secure-props (Packagist): affected from 1.2.0; fixed in 1.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-28864/ (Markdown: https://insights.sbomify.com/CVE-2024-28864/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28864
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28864
- OSV: https://osv.dev/vulnerability/CVE-2024-28864

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-28864/
Summaries are generated and may contain mistakes; the official description above is the record.