{"answers":{"affected":"2 open source packages ship an affected version, including ilicmiljan/secure-props. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-28864 in the wild and no public exploit code.","fix":"Upgrade ilicmiljan/secure-props to 1.2.2 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-28864 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2024-28864 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ilicmiljan/secure-props (Packagist): affected from 1.2.0; fixed in 1.2.2\n- ilicmiljan/secure-props (Packagist): affected from 1.2.0; fixed in 1.2.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-28864/ (Markdown: https://insights.sbomify.com/CVE-2024-28864/index.md)","id":"CVE-2024-28864","markdown":"https://insights.sbomify.com/CVE-2024-28864/index.md","name":"CVE-2024-28864","record":{"aliases":["GHSA-rj29-j2g4-77q8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP encryption library","requires_auth":"low_privilege","summary":"Attackers can retrieve plaintext data from encrypted fields when using TagAwareCipher with NullEncoder due to regex failure, exposing sensitive information.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"secureprops","vendor":"ilicmiljan"}],"cvss":{"score":2.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"[TagAwareCipher] - Decryption Failure (Regex Match)","id":"CVE-2024-28864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"django-wiki denial of service via regular expression","id":"CVE-2024-28865"},"packages":[{"ecosystem":"Packagist","fixed":["1.2.2"],"introduced":["1.2.0"],"last_affected":[],"package":"ilicmiljan/secure-props","purl":null,"source":"GHSA-rj29-j2g4-77q8"},{"ecosystem":"Packagist","fixed":["1.2.2"],"introduced":["1.2.0"],"last_affected":[],"package":"ilicmiljan/secure-props","purl":"pkg:composer/ilicmiljan/secure-props","source":"GHSA-rj29-j2g4-77q8"}],"prev":{"headline":"node-tar vulnerable to denial of service while parsing a tar file due to lack of folders count validation","id":"CVE-2024-28863"},"products":["Secure-Props"],"published":"2024-03-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["IlicMiljan"]},"summary":"Attackers can retrieve plaintext data from encrypted fields when using TagAwareCipher with NullEncoder due to regex failure, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2024-28864/"}