{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.unomi:unomi. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31164 in the wild and no public exploit code.","fix":"Upgrade org.apache.unomi:unomi to 1.5.5 or later.","what":"CVE-2021-31164 is a high-severity vulnerability in Apache Unomi, published on 4 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-31164 and fix it if it is affected.\n\nWhat it is: CVE-2021-31164 is a high-severity vulnerability in Apache Unomi, published on 4 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-31164 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.unomi:unomi (Maven): affected all versions; fixed in 1.5.5\n- org.apache.unomi:unomi (Maven): affected all versions; fixed in 1.5.5\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-2021-31164/ (Markdown: https://insights.sbomify.com/CVE-2021-31164/index.md)","id":"CVE-2021-31164","markdown":"https://insights.sbomify.com/CVE-2021-31164/index.md","name":"CVE-2021-31164","record":{"aliases":["GHSA-rm7f-mpcj-w4f6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Unomi","requires_auth":"none","summary":"Attackers can inject CRLF characters into logs due to missing escaping, potentially corrupting log files or misleading log analysis.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"unomi","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"Apache Unomi prior to version 1.5.5 allows CRLF log injection because of the lack of escaping in the log statements.","ecosystems":["Maven"],"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":"Apache Unomi log injection","id":"CVE-2021-31164","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Windows Container Manager Service Elevation of Privilege Vulnerability","id":"CVE-2021-31165"},"packages":[{"ecosystem":"Maven","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"org.apache.unomi:unomi","purl":null,"source":"GHSA-rm7f-mpcj-w4f6"},{"ecosystem":"Maven","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"org.apache.unomi:unomi","purl":"pkg:maven/org.apache.unomi/unomi","source":"GHSA-rm7f-mpcj-w4f6"}],"prev":{"headline":"Use after free in n/a","id":"CVE-2021-31162"},"products":["Apache Unomi"],"published":"2021-05-04","related":[{"cvss_score":9.8,"headline":"Remote Code Execution in Apache Unomi","id":"CVE-2020-13942","kev_date_added":null,"published":"2020-11-24"},{"cvss_score":9.8,"headline":"Improper Input Validation in Apache Unomi","id":"CVE-2020-11975","kev_date_added":null,"published":"2020-06-05"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Apache Software Foundation"]},"summary":"Attackers can inject CRLF characters into logs due to missing escaping, potentially corrupting log files or misleading log analysis.","url":"https://insights.sbomify.com/CVE-2021-31164/"}