CERTFR-2016-AVI-250
Vulnerability from certfr_avis - Published: 2016-07-25 - Updated: 2016-07-25
De multiples vulnérabilités ont été corrigées dans SCADA les produits Siemens. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un contournement de la politique de sécurité et une atteinte à la confidentialité des données.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Siemens | N/A | Siemens WinCC V7.4 sans la mise à jour de sécurité U1 | ||
| Siemens | N/A | Siemens SINEMA Remote Connect Server versions antérieures à 1.2 | ||
| Siemens | N/A | Siemens PCS 7 V8.1 SP1 avec WinCC V7.3 sans la mise à jour de sécurité U10, SIMATIC BATCH V8.1 SP1 sans la mise à jour de sécurité U9, OpenPCS 7 V8.1 sans la mise à jour de sécurité U3 | ||
| Siemens | N/A | Siemens SIMATIC NET PC-Software versions antérieures à V13 SP2 | ||
| Siemens | N/A | Siemens WinCC V7.3 sans la mise à jour de sécurité U10 | ||
| Siemens | N/A | Siemens PCS 7 V8.2 avec WinCC V7.4 sans la mise à jour de sécurité U1, OpenPCS 7 V8.2 sans la mise à jour de sécurité U3 | ||
| Siemens | N/A | Siemens WinCC Runtime Professional V13 versions antérieures à WinCC Runtime Professional V13 SP1 U9 |
| Title | Publication Time | Tags | |
|---|---|---|---|
|
|
|||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Siemens WinCC V7.4 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U1",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
},
{
"description": "Siemens SINEMA Remote Connect Server versions ant\u00e9rieures \u00e0 1.2",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
},
{
"description": "Siemens PCS 7 V8.1 SP1 avec WinCC V7.3 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U10, SIMATIC BATCH V8.1 SP1 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U9, OpenPCS 7 V8.1 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U3",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
},
{
"description": "Siemens SIMATIC NET PC-Software versions ant\u00e9rieures \u00e0 V13 SP2",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
},
{
"description": "Siemens WinCC V7.3 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U10",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
},
{
"description": "Siemens PCS 7 V8.2 avec WinCC V7.4 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U1, OpenPCS 7 V8.2 sans la mise \u00e0 jour de s\u00e9curit\u00e9 U3",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
},
{
"description": "Siemens WinCC Runtime Professional V13 versions ant\u00e9rieures \u00e0 WinCC Runtime Professional V13 SP1 U9",
"product": {
"name": "N/A",
"vendor": {
"name": "Siemens",
"scada": true
}
}
}
],
"affected_systems_content": null,
"content": "## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2016-5743",
"url": "https://www.cve.org/CVERecord?id=CVE-2016-5743"
},
{
"name": "CVE-2016-6204",
"url": "https://www.cve.org/CVERecord?id=CVE-2016-6204"
},
{
"name": "CVE-2016-5874",
"url": "https://www.cve.org/CVERecord?id=CVE-2016-5874"
},
{
"name": "CVE-2016-5744",
"url": "https://www.cve.org/CVERecord?id=CVE-2016-5744"
}
],
"initial_release_date": "2016-07-25T00:00:00",
"last_revision_date": "2016-07-25T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 SCADA SSA-453276 Siemens du 22 juillet 2016",
"url": "http://www.siemens.com/cert/pool/cert/siemens_security_advisory_SSA-453276.pdf"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 SCADA SSA-119132 Siemens du 22 juillet 2016",
"url": "http://www.siemens.com/cert/pool/cert/siemens_security_advisory_SSA-119132.pdf"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 SCADA SSA-378531 Siemens du 22 juillet 2016",
"url": "http://www.siemens.com/cert/pool/cert/siemens_security_advisory_SSA-378531.pdf"
}
],
"reference": "CERTFR-2016-AVI-250",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2016-07-25T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Injection de code indirecte \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans \u003cspan\nclass=\"textit\"\u003eSCADA les produits Siemens\u003c/span\u003e. Certaines d\u0027entre\nelles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code\narbitraire \u00e0 distance, un contournement de la politique de s\u00e9curit\u00e9 et\nune atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans SCADA les produits Siemens",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 SCADA SSA-453276 Siemens du 22 juillet 2016",
"url": null
},
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 SCADA SSA-378531 Siemens du 22 juillet 2016",
"url": null
},
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 SCADA SSA-119132 Siemens du 22 juillet 2016",
"url": null
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.