CVE-2023-38035
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability in MICS Admin Portal in Ivanti MobileIron Sentry versions 9.18.0 and below, which may allow an attacker to bypass authentication controls on the administrative interface due to an insufficiently restrictive Apache HTTPD configuration.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe MICS Admin Portal in Ivanti MobileIron Sentry versions 9.18.0 and below contains an authentication bypass vulnerability caused by an insufficiently restrictive Apache HTTPD configuration. Attackers can access the administrative interface without valid credentials by exploiting this misconfiguration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 9.18.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ivanti MobileIron Sentry versionCheck the product version through the admin console, system information page, or by querying the Sentry service. On the appliance, you can typically find version info in /opt/mobileiron/etc/version or through the MICS admin interface under System > About.Affected if The installed version is 9.18.0 or any version lower than 9.18.0 (any version <= 9.18.0 is affected)
-
Verify MICS Admin Portal accessibilityAttempt to access the MICS Admin Portal endpoint (typically /mics or /admin) from an unauthenticated browser session or using curl/wget without providing credentials: curl -k https://<sentry-host>/micsAffected if The portal returns administrative interface content or login prompts without requiring authentication, indicating the path is publicly accessible
-
Inspect Apache HTTPD configuration for authentication controlsLocate and review the Apache HTTPD configuration files for the MICS Admin Portal. Look for directives like Require, AuthType, or authentication blocks. Check configuration files in /etc/httpd/conf.d/ or similar paths depending on the Sentry installation.Affected if The Apache configuration lacks Require valid-user or similar authentication directives for administrative paths, or explicitly permits unauthenticated access to admin endpoints
You are affected if your Ivanti MobileIron Sentry version is 9.18.0 or below AND the MICS Admin Portal or its Apache configuration allows unauthenticated access to administrative functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedRestrict Apache HTTPD configuration to enforce proper authentication requirements on the MICS Admin Portal endpoints. Apply vendor patches when available and verify administrative interfaces are not exposed to unauthenticated access.
Upgrade to MobileIron Sentry version above 9.18.0 (contact Ivanti for the exact fixed release number)
- 1. Identify the current MobileIron Sentry version by accessing the admin interface or checking system documentation
- 2. Obtain the latest patched version from Ivanti's official support channels or software distribution portal
- 3. Review Ivanti's upgrade documentation for MobileIron Sentry
- 4. Perform a complete backup of the current configuration
- 5. Follow the standard upgrade procedure documented by Ivanti for MobileIron Sentry
- 6. Verify the upgrade was successful by checking the version number in the admin interface
- 7. Test authentication functionality on the MICS Admin Portal to confirm the vulnerability is resolved
- 8. Review Apache HTTPD configuration to ensure restrictive access controls are in place per Ivanti hardening guides
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-38035 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data