Comparison Overview
Saint-Gobain Eastern Mediterranean and Middle East
Saint-Gobain Eastern Mediterranean and Middle East
Mitsulift Bldg, 3rd Floor, P.O.Box 55-44, Dbayeh, Beirut / Lebanon, LB, +961 4 546870/1/2
Last Update: 28/02/2026
Saint-Gobain Eastern Mediterranean and Middle East (EMME) covers the activities of Saint-Gobain subsidiaries located in 13 Countries: Lebanon, Jordan, UAE, Qatar, Kuwait, KSA, Oman, Egypt, Iraq and Turkey, Libya, Tunisia, Turkmenistan & Sudan facilitating the group inte...
Knauf
Am Bahnhof 7, Iphofen, D-97346, DE
Last Update: 08/09/2026
Everyone sees opportunity differently. Knauf sees opportunity in everyone. Similar to other global businesses, our 41,500 team members in 90 countries across 300 sites provide a huge opportunity for anyone with ambition and energy. Unlike other global businesses, you ...
Compliance Ranges Comparison
Saint-Gobain Eastern Mediterranean and Middle East
Knauf
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Saint-Gobain Eastern Mediterranean and Middle East in 2026.
Incidents vs Wholesale Building Materials Industry Avg (This Year)
No incidents recorded for Knauf in 2026.
Incident History - Saint-Gobain Eastern Mediterranean and Middle East (X = Date, Y = Severity)
Saint-Gobain Eastern Mediterranean and Middle East cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Knauf (X = Date, Y = Severity)
Knauf cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Saint-Gobain Eastern Mediterranean and Middle East
Knauf
FAQ
Latest Global CVEs
OpenStack Ironic through 38.0.0 may send a username and password to an unexpected remote host when Image Service is configured for HTTP(S) Basic Authentication.
An issue was discovered in OpenStack Keystone before 29.0.3. Tokens obtained via delegated authentication methods (EC2 credentials, application credentials, OAuth1 access tokens, and trusts) are not blocked from creating, modifying, or deleting credentials via the /v3/credentials API. EC2-derived tokens can additionally read credential blobs, exposing TOTP MFA seeds and other secrets. Also, PATCH /v3/credentials does not validate the requested post-update project_id, allowing any delegated token to move a credential to an unauthorized project. All Keystone deployments using delegated authentication are affected.
The administrative password is hashed using a comparatively weak, fast algorithm for the credential store backing one authentication path, and the file containing that hash is written with permissions allowing it to be read by any local user. This is inconsistent with a separate, stronger hashing algorithm used for the same password on another authentication path. A party able to read this file, including a local user or a party with access to a configuration backup, could feasibly recover the underlying password through offline computation, compromising the administrative credential across every path that accepts it.
An example environment-configuration file for a bundled inventory-management component ships with a fixed, publicly-known administrative password. A deployment that copies this example file into active configuration without running the setup routine that regenerates credentials will expose that component's administrative interface to anyone aware of the default value.
A prior update that raised a bundled HTTP client library to a version remediating known vulnerabilities was later reverted, reintroducing the earlier, vulnerable version into a log-processing component. The only code path in that component using the library issues a request to a single fixed, trusted vendor URL at initialization and does not process attacker-controlled input through the library, limiting practical exploitability of the reintroduced version in this context.