{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32981 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32981 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32981 is a high-severity path traversal vulnerability in AVEVA System Platform, published on 4 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32981 and fix it if it is affected.\n\nWhat it is: CVE-2021-32981 is a high-severity path traversal vulnerability in AVEVA System Platform, published on 4 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32981 in the wild and no public exploit code.\n\nAffected product: AVEVA System Platform. 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-32981/ (Markdown: https://insights.sbomify.com/CVE-2021-32981/index.md)","id":"CVE-2021-32981","markdown":"https://insights.sbomify.com/CVE-2021-32981/index.md","name":"CVE-2021-32981","record":{"aliases":["GHSA-w5wr-x6gc-hqrq"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AVEVA System Platform","requires_auth":"high_privilege","summary":"Attackers can traverse restricted directories to read or modify files outside the intended scope in AVEVA System Platform.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"system_platform","vendor":"aveva"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"AVEVA System Platform versions 2017 through 2020 R2 P01 uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.","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":"AVEVA System Platform Path Traversal","id":"CVE-2021-32981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Automation Direct CLICK PLC CPU Modules Cleartext Transmission of Sensitive Information","id":"CVE-2021-32982"},"packages":[],"prev":{"headline":"Automation Direct CLICK PLC CPU Modules Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2021-32980"},"products":["AVEVA System Platform"],"published":"2022-04-04","related":[{"cvss_score":8.8,"headline":"AVEVA System Platform Missing Authentication for Critical Function","id":"CVE-2021-33008","kev_date_added":null,"published":"2022-04-04"},{"cvss_score":8.1,"headline":"AVEVA System Platform Cleartext Storage of Sensitive Information in Memory","id":"CVE-2022-0835","kev_date_added":null,"published":"2022-04-11"},{"cvss_score":7.5,"headline":"AVEVA System Platform Uncaught Exception","id":"CVE-2021-33010","kev_date_added":null,"published":"2022-04-04"},{"cvss_score":7.2,"headline":"AVEVA System Platform Improper Verification of Cryptographic Signature","id":"CVE-2021-32977","kev_date_added":null,"published":"2022-04-04"},{"cvss_score":7.2,"headline":"AVEVA System Platform Origin Validation Error","id":"CVE-2021-32985","kev_date_added":null,"published":"2022-04-04"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-16","vendors":["AVEVA"]},"summary":"Attackers can traverse restricted directories to read or modify files outside the intended scope in AVEVA System Platform.","url":"https://insights.sbomify.com/CVE-2021-32981/"}