CERTFR-2025-ALE-007
Vulnerability from certfr_alerte - Published: 2025-05-14 - Updated: 2025-06-24
[Mise à jour du 15 mai 2025]
Une preuve de concept est publiquement disponible sur Internet.
[Publication initiale]
Le 13 mai 2025, Ivanti a publié deux avis de sécurité concernant les vulnérabilités CVE-2025-4427 et CVE-2025-4428. L'utilisation combinée de ces deux vulnérabilités permet l'exécution de code arbitraire à distance pour un utilisateur non authentifié.
Ivanti indique que ces vulnérabilités sont activement exploitées.
Solutions
Le CERT-FR recommande l'application des correctifs dans les plus brefs délais.
Ivanti indique que la mise en place de listes de contrôle d'accès au niveau de l'API [1] permet de limiter la menace. De plus l'éditeur peut mettre à disposition une mesure de contournement sous la forme d'un fichier RPM.
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Ivanti | Endpoint Manager Mobile (EPMM) | Endpoint Manager Mobile versions 11.12.0.x antérieures à 11.12.0.5 | ||
| Ivanti | Endpoint Manager Mobile (EPMM) | Endpoint Manager Mobile versions 12.5.0.x antérieures à 12.5.0.1 | ||
| Ivanti | Endpoint Manager Mobile (EPMM) | Endpoint Manager Mobile versions 12.3.0.x antérieures à 12.3.0.2 | ||
| Ivanti | Endpoint Manager Mobile (EPMM) | Endpoint Manager Mobile versions 12.4.0.x antérieures à 12.4.0.2 |
| Title | Publication Time | Tags | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Endpoint Manager Mobile versions 11.12.0.x ant\u00e9rieures \u00e0 11.12.0.5",
"product": {
"name": "Endpoint Manager Mobile (EPMM)",
"vendor": {
"name": "Ivanti",
"scada": false
}
}
},
{
"description": "Endpoint Manager Mobile versions 12.5.0.x ant\u00e9rieures \u00e0 12.5.0.1",
"product": {
"name": "Endpoint Manager Mobile (EPMM)",
"vendor": {
"name": "Ivanti",
"scada": false
}
}
},
{
"description": "Endpoint Manager Mobile versions 12.3.0.x ant\u00e9rieures \u00e0 12.3.0.2",
"product": {
"name": "Endpoint Manager Mobile (EPMM)",
"vendor": {
"name": "Ivanti",
"scada": false
}
}
},
{
"description": "Endpoint Manager Mobile versions 12.4.0.x ant\u00e9rieures \u00e0 12.4.0.2",
"product": {
"name": "Endpoint Manager Mobile (EPMM)",
"vendor": {
"name": "Ivanti",
"scada": false
}
}
}
],
"affected_systems_content": "",
"closed_at": "2025-06-24",
"content": "## Solutions\n\nLe CERT-FR recommande l\u0027application des correctifs dans les plus brefs d\u00e9lais. \n\nIvanti indique que la mise en place de listes de contr\u00f4le d\u0027acc\u00e8s au niveau de l\u0027API [1] permet de limiter la menace. De plus l\u0027\u00e9diteur peut mettre \u00e0 disposition une mesure de contournement sous la forme d\u0027un fichier RPM. ",
"cves": [
{
"name": "CVE-2025-4427",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4427"
},
{
"name": "CVE-2025-4428",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4428"
}
],
"initial_release_date": "2025-05-14T00:00:00",
"last_revision_date": "2025-06-24T00:00:00",
"links": [
{
"title": "Avis CERT-FR CERTFR-2025-AVI-0400 du 13 mai 2025",
"url": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2025-AVI-0400/"
},
{
"title": "[1] Documentation d\u0027Ivanti relative \u00e0 l\u0027utilisation des listes de contr\u00f4le d\u0027acc\u00e8s",
"url": "https://help.ivanti.com/mi/help/en_us/core/12.x/sys/CoreSystemManager/Access_Control_Lists__Po.htm"
}
],
"reference": "CERTFR-2025-ALE-007",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2025-05-14T00:00:00.000000"
},
{
"description": "Une preuve de concept est publiquement disponible.",
"revision_date": "2025-05-15T00:00:00.000000"
},
{
"description": " Cl\u00f4ture de l\u0027alerte. Cela ne signifie pas la fin d\u0027une menace. Seule l\u0027application de la mise \u00e0 jour permet de vous pr\u00e9munir contre l\u0027exploitation de la vuln\u00e9rabilit\u00e9 correspondante.",
"revision_date": "2025-06-24T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "\u003cspan class=\"important-content\"\u003e[Mise \u00e0 jour du 15 mai 2025]\u003c/span\u003e\u003c/br\u003e\nUne preuve de concept est publiquement disponible sur Internet.\n\n[Publication initiale]\u003c/br\u003e\nLe 13 mai 2025, Ivanti a publi\u00e9 deux avis de s\u00e9curit\u00e9 concernant les vuln\u00e9rabilit\u00e9s CVE-2025-4427 et CVE-2025-4428. L\u0027utilisation combin\u00e9e de ces deux vuln\u00e9rabilit\u00e9s permet l\u0027ex\u00e9cution de code arbitraire \u00e0 distance pour un utilisateur non authentifi\u00e9. \n\nIvanti indique que ces vuln\u00e9rabilit\u00e9s sont activement exploit\u00e9es. ",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Ivanti Endpoint Manager Mobile (EPMM)",
"vendor_advisories": [
{
"published_at": "2025-05-13",
"title": "Bulletin de s\u00e9curit\u00e9 Ivanti epmm-security-update",
"url": "https://www.ivanti.com/blog/epmm-security-update"
},
{
"published_at": "2025-05-13",
"title": "Bulletin de s\u00e9curit\u00e9 Ivanti Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM",
"url": "https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM"
}
]
}
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.