{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35488 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35488 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35488 is a high-severity denial of service vulnerability in n/a, published on 5 Jan 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-2020-35488 and fix it if it is affected.\n\nWhat it is: CVE-2020-35488 is a high-severity denial of service vulnerability in n/a, published on 5 Jan 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-2020-35488 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-35488/ (Markdown: https://insights.sbomify.com/CVE-2020-35488/index.md)","id":"CVE-2020-35488","markdown":"https://insights.sbomify.com/CVE-2020-35488/index.md","name":"CVE-2020-35488","record":{"aliases":["GHSA-9rx5-vw74-rpgf"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"NXLog Community Edition","requires_auth":"none","summary":"Remote attackers can crash the NXLog daemon via crafted Syslog payloads when specific directory naming configurations are enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nxlog","vendor":"nxlog"}],"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:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The fileop module of the NXLog service in NXLog Community Edition 2.10.2150 allows remote attackers to cause a denial of service (daemon crash) via a crafted Syslog payload to the Syslog service. This attack requires a specific configuration. Also, the name of the directory created must use a Syslog field. (For example, on Linux it is not possible to create a .. directory. On Windows, it is not possible to create a CON directory.)","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2020-12-15","github_poc":2,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-12-15T17:55:07Z","kind":"github_poc","ref":"https://github.com/GuillaumePetit84/CVE-2020-35488","stars":1,"title":null},{"date":"2020-12-17","kind":"exploitdb","ref":"49283","stars":null,"title":"Nxlog Community Edition 2.10.2150 - DoS (Poc)"},{"date":"2021-10-12T18:25:17Z","kind":"github_poc","ref":"https://github.com/githubfoam/nxlog-ubuntu-githubactions","stars":0,"title":"nxlog ubuntu CVE-2020-35488"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2020-35488","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2020-35489"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2020-35483"},"products":["n/a"],"published":"2021-01-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can crash the NXLog daemon via crafted Syslog payloads when specific directory naming configurations are enabled.","url":"https://insights.sbomify.com/CVE-2020-35488/"}