{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-1774 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1774 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1774 is a medium-severity vulnerability in NASK - PIB BotSense, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1774 and fix it if it is affected.\n\nWhat it is: CVE-2025-1774 is a medium-severity vulnerability in NASK - PIB BotSense, published on 17 Mar 2025. 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-2025-1774 in the wild and no public exploit code.\n\nAffected product: NASK - PIB BotSense. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-1774/ (Markdown: https://insights.sbomify.com/CVE-2025-1774/index.md)","id":"CVE-2025-1774","markdown":"https://insights.sbomify.com/CVE-2025-1774/index.md","name":"CVE-2025-1774","record":{"aliases":["GHSA-w97p-2hwc-7qx6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"BotSense logging system","requires_auth":"none","summary":"Attackers can inject separator characters into BotSense logs, corrupting event data structure and potentially disrupting log analysis.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-143","name":"Improper Neutralization of Record Delimiters"},{"id":"CWE-142","name":"Improper Neutralization of Value Delimiters"}],"description":"Incorrect string encoding vulnerability in NASK - PIB BotSense allows injection of an additional field separator character or value in the content of some fields of the generated event. A field with additional field separator characters or values can be included in the \"extraData\" field.This issue affects BotSense in versions before 2.8.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Logs manipulation in BotSense","id":"CVE-2025-1774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-Site Scripting (XSS) vulnerability in Soteshop","id":"CVE-2025-1776"},"packages":[],"prev":{"headline":"Traveler \u003c= 3.1.8 - Reflected Cross-Site Scripting","id":"CVE-2025-1773"},"products":["BotSense"],"published":"2025-03-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-03-17","vendors":["NASK - PIB"]},"summary":"Attackers can inject separator characters into BotSense logs, corrupting event data structure and potentially disrupting log analysis.","url":"https://insights.sbomify.com/CVE-2025-1774/"}