[TagAwareCipher] - Decryption Failure (Regex Match)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

2.6 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-28864: 0.33% estimated exploitation activity in the next 30 days; percentile 25.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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). Patches The patch for the issue has been released. Users are advised to update to version 1.2.2. 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…

Published by the source

18 Mar 2024, 20:39 UTC

Last modified by the source

19 Mar 2024, 18:30 UTC

Source last checked

26 Oct 2026, 14:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rj29-j2g4-77q8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28864

Advisory: [TagAwareCipher] - Decryption Failure (Regex Match)
IDs: CVE-2024-28864, GHSA-rj29-j2g4-77q8
Record: https://patchnext.com/advisories/cve-2024-28864 (revision 1, source checked 26 Oct 2026, 14:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ilicmiljan/secure-props 1.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ilicmiljan/secure-props: affected >= 1.2.0, < 1.2.2; fixed in 1.2.2

## Suggested inspection (read-only)
- Packagist ilicmiljan/secure-props: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ilicmiljan/secure-props.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rj29-j2g4-77q8 (GitHub-reviewed advisory GHSA-rj29-j2g4-77q8 lists affected ranges: Packagist ilicmiljan/secure-props >=1.2.0 <1.2.2)

Commands are suggestions: review each one before running it.