Threats / Ivanti / CVE-2023-35078
CVE-2023-35078
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Ivanti Endpoint Manager Mobile (EPMM) vulnerability
Ivanti Endpoint Manager Mobile contains an authentication bypass in specific API paths, allowing unauthenticated access to user PII, device details, and configuration changes including software installation and security profile modification
Verdict
Today item, not a backlog item.
An unauthenticated attacker can bypass authentication controls to access sensitive user and device information, and modify security configurations on mobile devices managed by vulnerable EPMM instances.
CISA KEV Yes · 2023-07-253Ransomware use Flagged3EPSS 0.99999 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
892 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-07-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Ivanti, Endpoint Manager Mobile (EPMM). Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-287 Improper Authentication — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify and access unprotected API endpoints without credentials to enumerate user identities and device information.
Business
Exposure of personally identifiable information creates privacy breach liability and regulatory compliance violations.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I modify security profiles and install unauthorized software on enrolled mobile devices through the same unauthenticated API access.
Business
Compromise of device security posture enables malware distribution and loss of control over corporate mobile infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage device compromise and PII access to support lateral movement and credential harvesting across the organization.
Business
Expanded attack surface enables ransomware deployment and data exfiltration targeting enterprise systems and sensitive assets.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05