CVE-2023-46808
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 · uneditedAn file upload vulnerability in Ivanti ITSM before 2023.4, allows an authenticated remote user to perform file writes to the server. Successful exploitation may lead to execution of commands in the context of non-root user.
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 · high confidenceIvanti ITSM versions before 2023.4 contain an authenticated file upload vulnerability allowing a remote authenticated user to write arbitrary files to the server. Successful exploitation can lead to command execution in the context of a non-root user.
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< 2023.4CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 if Ivanti Neurons For ITSM is installedLocate the Ivanti ITSM application installation directory or check system services for Ivanti-related processesAffected if The application is present on the system
-
Determine the installed version of Ivanti Neurons For ITSMCheck the application version through the admin console, installation directory, or version file provided with the productAffected if The installed version is any version before 2023.4
-
Verify if file upload functionality is enabledAccess the admin console and navigate to the file upload or attachment settings. Check if file upload features are accessible to authenticated usersAffected if File upload functionality is enabled and accessible to authenticated users
-
Review access logs for suspicious file upload activityExamine application and web server logs for anomalous upload requests, particularly those involving executable file types or uploads to unexpected directoriesAffected if Log entries show unauthorized or suspicious file uploads to non-standard directories
You are affected if Ivanti Neurons For ITSM is installed with a version lower than 2023.4 and the file upload feature is accessible to authenticated users.
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 · scoped2023.4
Upgrade Ivanti ITSM to version 2023.4 or later. Additionally, restrict file upload functionality to only necessary file types, implement strict validation on uploaded file contents, and limit the upload directory permissions.
2023.4
- Back up the current Ivanti Neurons for ITSM installation and database before proceeding with any upgrade.
- Review the official Ivanti upgrade documentation and release notes for version 2023.4 to understand prerequisites and migration requirements.
- Download Ivanti Neurons for ITSM version 2023.4 or later from the official Ivanti download portal (typically available through the Ivanti Customer Portal or authorized distribution channels).
- Follow the standard Ivanti upgrade procedure: stop the ITSM services, run the upgrade installer, and apply any required database migrations.
- Restart the ITSM services and verify that the application functions normally.
- Confirm the upgrade was successful by checking the ITSM version information within the admin interface.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46808 — 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-46808 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