FlawAtlas
Search the atlas
SUSE-SU-2017:0424-1 Not scored

Security update for expat

This update for expat fixes the following security issues: - CVE-2012-6702: Expat, when used in a parser that has not called XML_SetHashSalt or passed it a seed of 0, made it easier for context-dependent attackers to defeat cryptographic protection mechanisms via vectors involving use of the srand function. (bsc#983215) - CVE-2016-5300: The XML parser in Expat did not use sufficient entropy for hash initialization, which allowed context-dependent attackers to cause a denial of service (CPU consumption) via crafted identifiers in an XML document. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-0876. (bsc#983216)

Exploit probability Not scored
Published February 8, 2017
Required by Not available
Last source change February 4, 2026

02 / AFFECTED SOFTWARE

Affected packages

SUSE:Linux Enterprise Desktop 12 SP1 expat
SUSE:Linux Enterprise Desktop 12 SP2 expat
SUSE:Linux Enterprise Server 12 SP1 expat
SUSE:Linux Enterprise Server 12 SP2 expat
SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 expat
SUSE:Linux Enterprise Server for SAP Applications 12 SP1 expat
SUSE:Linux Enterprise Server for SAP Applications 12 SP2 expat
SUSE:Linux Enterprise Software Development Kit 12 SP1 expat
SUSE:Linux Enterprise Software Development Kit 12 SP2 expat

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities SUSE-SU-2017:0424-1

This update for expat fixes the following security issues: - CVE-2012-6702: Expat, when used in a parser that has not called XML_SetHashSalt or passed it a seed of 0, made it easier for context-dependent attackers to defeat cryptographic protection mechanisms via vectors involving use of the srand function. (bsc#983215) - CVE-2016-5300: The XML parser in Expat did not use sufficient entropy for hash initialization, which allowed context-dependent attackers to cause a denial of service (CPU consumption) via crafted identifiers in an XML document. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-0876. (bsc#983216)

View original source

05 / REFERENCES

Further evidence