basicsecurity.net
Proof, not just disclosure.
Threats / Ivanti / CVE-2023-38035
CVE-2023-38035 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Ivanti Sentry vulnerability

Ivanti Sentry contains an authentication bypass vulnerability in its administrative interface due to insufficiently restrictive Apache HTTPD configuration, allowing attackers to circumvent access controls.

Verdict

Today item, not a backlog item.

An attacker can bypass authentication on the Sentry administrative interface through misconfigured Apache HTTPD settings, gaining unauthorized administrative access. This vulnerability is actively exploited in the wild and associated with ransomware campaigns.

CISA KEV Yes · 2023-08-223Ransomware use Flagged3EPSS 0.99949 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
252 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-08-22), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99949 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Ivanti, Sentry. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-863 Incorrect Authorization — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-863 · Incorrect AuthorizationAuthorization / access control
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I exploit the Apache HTTPD misconfiguration to bypass authentication checks on the admin interface.
Business
Unauthorized administrative access is gained, exposing the entire mobile device management infrastructure to compromise.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I establish persistent control over the Sentry platform to pivot into managed mobile devices and corporate networks.
Business
Mobile device fleet and connected enterprise systems become compromised, enabling data exfiltration and lateral movement.
3

Lateral reach — past segmentation narrative 3

Attacker
I deploy ransomware payloads across managed devices and infrastructure as part of an organized campaign.
Business
Operations are disrupted through widespread encryption of critical systems and devices, triggering ransom demands and recovery costs.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 252 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by hackerone (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by hackeroneCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.