{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16691 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16691 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16691 is a medium-severity vulnerability in SAP Note Assistant, published on 12 Dec 2017. 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-2017-16691 and fix it if it is affected.\n\nWhat it is: CVE-2017-16691 is a medium-severity vulnerability in SAP Note Assistant, published on 12 Dec 2017. 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-2017-16691 in the wild and no public exploit code.\n\nAffected product: SAP Note Assistant. 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-2017-16691/ (Markdown: https://insights.sbomify.com/CVE-2017-16691/index.md)","id":"CVE-2017-16691","markdown":"https://insights.sbomify.com/CVE-2017-16691/index.md","name":"CVE-2017-16691","record":{"aliases":["GHSA-4f5h-cfp2-m9r7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SAP Note Assistant","requires_auth":"none","summary":"Attackers can bypass digital signature verification in SAP Note Assistant to extract tampered files, potentially leading to code execution.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"sap","cpe":[{"product":"business_application_software_integrated_solution","vendor":"sap"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"SAP Note Assistant tool (SAP BASIS from 7.00 to 7.02, from 7.10 to 7.11, 7.30, 7.31,7.40, from 7.50 to 7.52) supports upload of digitally signed note file of type 'SAR'. The digital signature verification is done together with the extraction of note file contained in the SAR archive. It is possible to append a tampered file to the SAR archive using SAPCAR tool and during the extraction, digital signature verification fails but the tampered file is extracted.","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":"Security feature bypass in SAP Note Assistant","id":"CVE-2017-16691","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2017-16709"},"packages":[],"prev":{"headline":"Other in SAP Plant Connectivity","id":"CVE-2017-16690"},"products":["SAP Note Assistant"],"published":"2017-12-12","related":[{"cvss_score":8.8,"headline":"Missing authorization in SAP BASIS","id":"CVE-2019-0279","kev_date_added":null,"published":"2019-04-10"},{"cvss_score":8.8,"headline":"Path traversal in SAP BASIS (ABAP File Interface)","id":"CVE-2018-2367","kev_date_added":null,"published":"2018-03-01"},{"cvss_score":8.8,"headline":"Code injection in SAP NetWeaver","id":"CVE-2018-2363","kev_date_added":null,"published":"2018-01-09"},{"cvss_score":8,"headline":"Missing authorization in SAP Basis (ABAP Platform)","id":"CVE-2018-2494","kev_date_added":null,"published":"2018-12-11"},{"cvss_score":7.2,"headline":"Code injection in SAP NetWeaver Internet Transaction Server (ITS)","id":"CVE-2017-16682","kev_date_added":null,"published":"2017-12-12"}],"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-17","vendors":["SAP"]},"summary":"Attackers can bypass digital signature verification in SAP Note Assistant to extract tampered files, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2017-16691/"}