Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY13 SECURITY RECORDS

SAP SE

SAP Internet Graphics Server

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2018-2396 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2395 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2394 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2393 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2392 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2389 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2388 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2387 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2386 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2385 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2384 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2383 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2018-2382 14 Feb 2018 7.20; 7.20EXT; 7.45; 7.49; 7.53 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.