CERTFR-2026-AVI-1275
Vulnerability from certfr_avis - Published: 2026-10-07 - Updated: 2026-10-07
De multiples vulnérabilités ont été découvertes dans Sonicwall Secure Mobile Access. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une falsification de requêtes côté serveur (SSRF) et une injection de code indirecte à distance (XSS).
L'éditeur ne fait pas mention d'exploitations actives pour le moment.
Cependant, le CERT-FR rappelle que des combinaisons de deux vulnérabilités, l'une permettant à un attaquant authentifié d'exécuter du code arbitraire à distance, facilitée par l'autre (de type SSRF) permettant de contourner cette authentification, ont déjà été activement exploitées à plusieurs reprises cette année sur ce produit (cf. section Documentation).
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Sonicwall | Secure Mobile Access | SMA1000 versions antérieures à 12.4.3-03670 | ||
| Sonicwall | Secure Mobile Access | SMA1000 versions 12.5 antérieures à 12.5.0-03082 |
| Title | Publication Time | Tags | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "SMA1000 versions ant\u00e9rieures \u00e0 12.4.3-03670",
"product": {
"name": "Secure Mobile Access",
"vendor": {
"name": "Sonicwall",
"scada": false
}
}
},
{
"description": "SMA1000 versions 12.5 ant\u00e9rieures \u00e0 12.5.0-03082",
"product": {
"name": "Secure Mobile Access",
"vendor": {
"name": "Sonicwall",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-102256",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102256"
},
{
"name": "CVE-2026-102255",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102255"
},
{
"name": "CVE-2026-102258",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102258"
},
{
"name": "CVE-2026-102257",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102257"
}
],
"initial_release_date": "2026-10-07T00:00:00",
"last_revision_date": "2026-10-07T00:00:00",
"links": [
{
"title": "Alerte CERT-FR CERTFR-2026-ALE-006 du 15 juillet 2026",
"url": "/alerte/CERTFR-2026-ALE-006/"
},
{
"title": "Alerte CERT-FR CERTFR-2026-ALE-009 du 02 septembre 2026",
"url": "/alerte/CERTFR-2026-ALE-009/"
}
],
"reference": "CERTFR-2026-AVI-1275",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-10-07T00:00:00.000000"
}
],
"risks": [
{
"description": "Injection de code indirecte \u00e0 distance (XSS)"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Falsification de requ\u00eates c\u00f4t\u00e9 serveur (SSRF)"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Sonicwall Secure Mobile Access. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une falsification de requ\u00eates c\u00f4t\u00e9 serveur (SSRF) et une injection de code indirecte \u00e0 distance (XSS).\n\nL\u0027\u00e9diteur ne fait pas mention d\u0027exploitations actives pour le moment.\u003cbr\u003e\nCependant, le CERT-FR rappelle que des combinaisons de deux vuln\u00e9rabilit\u00e9s, l\u0027une permettant \u00e0 un attaquant authentifi\u00e9 d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance, facilit\u00e9e par l\u0027autre (de type SSRF) permettant de contourner cette authentification, ont d\u00e9j\u00e0 \u00e9t\u00e9 activement exploit\u00e9es \u00e0 plusieurs reprises cette ann\u00e9e sur ce produit (cf. section Documentation).",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Sonicwall Secure Mobile Access",
"vendor_advisories": [
{
"published_at": "2026-10-06",
"title": "Bulletin de s\u00e9curit\u00e9 SonicWall SNWLID-2026-0017",
"url": "https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0017"
}
]
}
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.