{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3975 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3975 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3975 is a high-severity memory corruption vulnerability in The Atlantis Word Processor Team Atlantis Word Processor, published on 1 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-3975 and fix it if it is affected.\n\nWhat it is: CVE-2018-3975 is a high-severity memory corruption vulnerability in The Atlantis Word Processor Team Atlantis Word Processor, published on 1 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-3975 in the wild and no public exploit code.\n\nAffected product: The Atlantis Word Processor Team Atlantis Word Processor. 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-2018-3975/ (Markdown: https://insights.sbomify.com/CVE-2018-3975/index.md)","id":"CVE-2018-3975","markdown":"https://insights.sbomify.com/CVE-2018-3975/index.md","name":"CVE-2018-3975","record":{"aliases":["GHSA-6wh2-mpvp-28q3"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Word processor","requires_auth":"none","summary":"A specially crafted RTF file can trigger an out-of-bounds write via an uninitialized variable, potentially allowing arbitrary code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"atlantis_word_processor","vendor":"atlantiswordprocessor"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An exploitable uninitialized variable vulnerability exists in the RTF-parsing functionality of Atlantis Word Processor 3.2.6 version. A specially crafted RTF file can leverage an uninitialized stack address, resulting in an out-of-bounds write, which in turn could lead to code execution.","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":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-3975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in ACD Systems","id":"CVE-2018-3976"},"packages":[],"prev":{"headline":"Privilege escalation in GOG Galaxy","id":"CVE-2018-3974"},"products":["Atlantis Word Processor"],"published":"2018-10-01","related":[{"cvss_score":8.8,"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-3983","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":8.8,"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-4038","kev_date_added":null,"published":"2018-12-01"},{"cvss_score":8.8,"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-4039","kev_date_added":null,"published":"2018-12-01"},{"cvss_score":8.8,"headline":"Null dereference in Atlantis Word Processor","id":"CVE-2018-4040","kev_date_added":null,"published":"2018-12-01"},{"cvss_score":8.8,"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-3978","kev_date_added":null,"published":"2018-10-01"},{"cvss_score":8.8,"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-3982","kev_date_added":null,"published":"2018-10-01"},{"cvss_score":8.8,"headline":"Memory corruption in Atlantis Word Processor","id":"CVE-2018-3984","kev_date_added":null,"published":"2018-10-01"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["The Atlantis Word Processor Team"]},"summary":"A specially crafted RTF file can trigger an out-of-bounds write via an uninitialized variable, potentially allowing arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2018-3975/"}