{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-38479 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-38479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-38479 is a medium-severity memory corruption vulnerability in AUVESY Versiondog, published on 22 Oct 2021. 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-2021-38479 and fix it if it is affected.\n\nWhat it is: CVE-2021-38479 is a medium-severity memory corruption vulnerability in AUVESY Versiondog, published on 22 Oct 2021. 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-2021-38479 in the wild and no public exploit code.\n\nAffected product: AUVESY Versiondog. 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-2021-38479/ (Markdown: https://insights.sbomify.com/CVE-2021-38479/index.md)","id":"CVE-2021-38479","markdown":"https://insights.sbomify.com/CVE-2021-38479/index.md","name":"CVE-2021-38479","record":{"aliases":["GHSA-27q3-p62g-44fr"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Versiondog asset management","requires_auth":"none","summary":"Attackers can exploit raw pointer handling in AUVESY Versiondog API to write arbitrary data to memory, potentially leading to code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"versiondog","vendor":"auvesy"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Many API function codes receive raw pointers remotely from the user and trust these pointers as valid in-bound memory regions. An attacker can manipulate API functions by writing arbitrary data into the resolved address of a raw pointer.","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":"AUVESY Versiondog","id":"CVE-2021-38479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"InHand Networks IR615 Router","id":"CVE-2021-38480"},"packages":[],"prev":{"headline":"InHand Networks IR615 Router","id":"CVE-2021-38478"},"products":["Versiondog"],"published":"2021-10-22","related":[{"cvss_score":9.8,"headline":"AUVESY Versiondog","id":"CVE-2021-38449","kev_date_added":null,"published":"2021-10-22"},{"cvss_score":9.8,"headline":"AUVESY Versiondog","id":"CVE-2021-38457","kev_date_added":null,"published":"2021-10-22"},{"cvss_score":9.8,"headline":"AUVESY Versiondog","id":"CVE-2021-38477","kev_date_added":null,"published":"2021-10-22"},{"cvss_score":9.1,"headline":"AUVESY Versiondog","id":"CVE-2021-38453","kev_date_added":null,"published":"2021-10-22"},{"cvss_score":9.1,"headline":"AUVESY Versiondog","id":"CVE-2021-38469","kev_date_added":null,"published":"2021-10-22"},{"cvss_score":9.1,"headline":"AUVESY Versiondog","id":"CVE-2021-38471","kev_date_added":null,"published":"2021-10-22"},{"cvss_score":8.2,"headline":"AUVESY Versiondog","id":"CVE-2021-38461","kev_date_added":null,"published":"2021-10-22"}],"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":["AUVESY"]},"summary":"Attackers can exploit raw pointer handling in AUVESY Versiondog API to write arbitrary data to memory, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2021-38479/"}