What is CVE-2024-28864?

CVE-2024-28864 is a low-severity inefficient regular expression (ReDoS) vulnerability in ilicmiljan/secure-props (composer), affecting versions >= 1.2.0, < 1.2.2. It is fixed in 1.2.2. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.

How severe is CVE-2024-28864?

CVE-2024-28864 has a CVSS score of 2.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of ilicmiljan/secure-props are affected by CVE-2024-28864?

ilicmiljan/secure-props (composer) versions >= 1.2.0, < 1.2.2 is affected.

Is there a fix for CVE-2024-28864?

Yes. CVE-2024-28864 is fixed in 1.2.2. Upgrade to this version or later.

Is CVE-2024-28864 exploitable, and should I be worried?

Whether CVE-2024-28864 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-28864 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-28864?

Upgrade ilicmiljan/secure-props to 1.2.2 or later.

CVE-2024-28864 in ilicmiljan/secure-props

Q: How severe is CVE-2024-28864?

CVE-2024-28864 has a CVSS score of 2.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of ilicmiljan/secure-props are affected by CVE-2024-28864?

ilicmiljan/secure-props (composer) versions >= 1.2.0, < 1.2.2 is affected.

Q: Is there a fix for CVE-2024-28864?

Yes. CVE-2024-28864 is fixed in 1.2.2. Upgrade to this version or later.

Q: Is CVE-2024-28864 exploitable, and should I be worried?

Whether CVE-2024-28864 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-28864 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-28864?

Upgrade ilicmiljan/secure-props to 1.2.2 or later.

Summary

[TagAwareCipher] - Decryption Failure (Regex Match)

Workarounds

The main recommendation is to update to the latest version as there are no breaking changes.

If that's not possible, you can 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 Base64Encoder by default.

References

Reported issue: https://github.com/IlicMiljan/Secure-Props/issues/20
Pull request resolving bug: https://github.com/IlicMiljan/Secure-Props/pull/21

Impact

Vulnerability in SecureProps 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).

A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use. Typical impact: denial of service when input is crafted to trigger backtracking.

CVE-2024-28864 has a CVSS score of 2.6 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.2); upgrading removes the vulnerable code path.

Affected versions

ilicmiljan/secure-props (>= 1.2.0, < 1.2.2)

Security releases

ilicmiljan/secure-props → 1.2.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The patch for the issue has been released. Users are advised to update to version 1.2.2.

Frequently Asked Questions

What is CVE-2024-28864? CVE-2024-28864 is a low-severity inefficient regular expression (ReDoS) vulnerability in ilicmiljan/secure-props (composer), affecting versions >= 1.2.0, < 1.2.2. It is fixed in 1.2.2. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
How severe is CVE-2024-28864? CVE-2024-28864 has a CVSS score of 2.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of ilicmiljan/secure-props are affected by CVE-2024-28864? ilicmiljan/secure-props (composer) versions >= 1.2.0, < 1.2.2 is affected.
Is there a fix for CVE-2024-28864? Yes. CVE-2024-28864 is fixed in 1.2.2. Upgrade to this version or later.
Is CVE-2024-28864 exploitable, and should I be worried? Whether CVE-2024-28864 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-28864 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-28864? Upgrade ilicmiljan/secure-props to 1.2.2 or later.