CVE-2023-34197
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 · uneditedZoho ManageEngine ServiceDesk Plus before 14202, ServiceDesk Plus MSP before 14300, and SupportCenter Plus before 14300 have a privilege escalation vulnerability in the Release module that allows unprivileged users to access the Reminders of a release ticket and make modifications.
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 confidenceThis is an insecure direct object reference (IDOR) vulnerability in the Release module of ManageEngine ServiceDesk Plus and SupportCenter Plus. Unprivileged users can access and modify Reminders associated with release tickets that should be restricted to higher-privileged roles, bypassing proper authorization checks in the application's access control logic.
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< 14.2= 14.2< 14.2= 14.2< 14.2= 14.2CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 the installed product and versionAccess the admin console and navigate to the About or version information page. For ServiceDesk Plus, typically found at /about.do or in the Admin > General > About section. For SupportCenter Plus, check Admin > Product Info > About.Affected if The installed version is ServiceDesk Plus or SupportCenter Plus version 14.2 or below (any version < 14.2 or exactly 14.2)
-
Confirm the Release module is in useCheck if the Release module is enabled and accessible in the application. Navigate to the Releases section or module in the main navigation. Verify if release tickets exist in the system.Affected if The Release module is active and contains release tickets in the environment
-
Verify low-privileged user access to the Release moduleLog in with a low-privilege account (a user without admin or manager roles) and attempt to navigate to the Release module. Check if such users can view, create, or edit release tickets.Affected if Low-privilege users can access the Release module without elevated permissions
-
Test for IDOR on Release RemindersAs a low-privilege user, attempt to access or modify Reminders associated with a release ticket. This can be done by accessing reminder endpoints directly or viewing reminders attached to releases that should be restricted to higher-privileged roles.Affected if Unprivileged users can view, access, or modify Reminders on release tickets that should be restricted to admin or manager roles
-
Review user role permissions for Release RemindersIn the admin console, navigate to Roles and Permissions configuration. Examine the permissions assigned to standard user roles regarding the Release module and Reminders functionality.Affected if Standard user roles are granted access to Release Reminders that should be limited to higher-privileged roles
Your environment is affected if you are running ServiceDesk Plus or SupportCenter Plus version 14.2 or below and low-privilege users can access the Release module and its Reminders functionality.
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 · scoped14.2
Upgrade ServiceDesk Plus to version 14202 or higher, ServiceDesk Plus MSP to 14300 or higher, and SupportCenter Plus to 14300 or higher. Alternatively, restrict low-privileged user access to the Release module until the patch is applied.
ServiceDesk Plus: 14202+; ServiceDesk Plus MSP: 14300+; SupportCenter Plus: 14300+
- 1. Identify the currently installed ManageEngine product (ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus) and its exact version/build number
- 2. For ServiceDesk Plus: Upgrade to version 14202 or later
- 3. For ServiceDesk Plus MSP: Upgrade to version 14300 or later
- 4. For SupportCenter Plus: Upgrade to version 14300 or later
- 5. After upgrade, verify the Release module Reminders functionality works correctly for appropriate privilege levels
- 6. Confirm unprivileged users can no longer access or modify Release ticket Reminders
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34197 — 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-34197 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