CVE-2023-36496
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 · uneditedDelegated Admin Privilege virtual attribute provider plugin, when enabled, allows an authenticated user to elevate their permissions in the Directory Server.
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 confidenceA privilege escalation vulnerability exists in the Delegated Admin Privilege virtual attribute provider plugin of a Directory Server. When this plugin is enabled, it incorrectly permits authenticated users to elevate their permissions beyond their assigned privileges, allowing unauthorized administrative access to the directory.
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>= 8.3.0.0, <= 8.3.0.8>= 9.0.0.0, <= 9.0.0.5>= 9.1.0.0, <= 9.1.0.2= 9.2.0.0= 9.2.0.1= 9.3.0.0= 9.3.0.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check Pingdirectory versionRun the dsversion command from the PingDirectory installation directory, or inspect the version file typically found in the installation rootAffected if The installed version falls within any of these ranges: 8.3.0.0-8.3.0.8, 9.0.0.0-9.0.0.5, 9.1.0.0-9.1.0.2, or equals 9.2.0.0, 9.2.0.1, 9.3.0.0, or 9.3.0.1
-
Verify the Delegated Admin Privilege plugin existsUse dsconfig --list-plugins to list all configured plugins and search for an entry named 'Delegated Admin Privilege Virtual Attribute Provider' or similarAffected if The plugin appears in the plugin list and is enabled
-
Confirm plugin is actively enabledRun dsconfig get-plugin-prop --plugin-name "Delegated Admin Privilege Virtual Attribute Provider" --prop enabled to check the enabled statusAffected if The plugin is present and the enabled property is set to true
-
Review plugin configuration for virtual attributeCheck the virtual attribute provider configuration using dsconfig and verify the Delegated Admin Privilege provider is configured as a virtual attribute in the directoryAffected if The virtual attribute provider is configured and active in the directory schema
If the Pingdirectory version is within the affected ranges AND the Delegated Admin Privilege virtual attribute provider plugin is enabled, the environment is vulnerable to privilege escalation.
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.
From vendor dataDisable the Delegated Admin Privilege virtual attribute provider plugin if not required, or apply vendor-provided security patches to address the improper permission handling. Review user privilege assignments after remediation.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36496 — 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-36496 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