CVE-2017-16691: SAP SAP Note Assistant vulnerability

CVE-2017-16691: 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...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 17, 2024, 00:31 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE affects SAP Note Assistant, a tool used to import SAP notes. A tampered file can be appended to a signed SAR archive; signature verification fails, but the tampered file is still extracted. That creates an integrity risk in a trusted maintenance workflow. Exposure is limited to SAP environments running the listed SAP BASIS versions where SAP Note Assistant imports SAR note files. The source bundle does not define network reachability, required privileges, or default exposure. Treat this as a maintenance-chain integrity issue. Prioritize SAP systems in scope, verify SAP Note 2546220 status, and ensure administrative controls prevent untrusted note files entering production workflows. Mitigation focus: Review SAP Note 2546220 and SAP December 2017 Security Patch Day guidance.; Confirm affected SAP BASIS systems have the vendor-recommended correction applied.; Restrict SAP Note Assistant usage to trusted administrators..

Prepared: Jun 12, 2026, 19:33 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-16691 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 12, 2017, 14:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://blogs.sap.com/2017/12/12/sap-security-patch-day-december-2017/CVE reference · x_refsource_CONFIRM
https://launchpad.support.sap.com/#/notes/2546220CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

SAPSAP Note AssistantSAP BASIS from 7.00 to 7.02, from 7.10 to 7.11, 7.30, 7.31,7.40, from 7.50 to 7.52Listed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.