dbcve.org
Symantec Identity Governance And AdministrationApplication · Broadcom

CVE-2022-25626

MEDIUM · 5.3 CVSS v3.1 Published 2022-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An unauthenticated user can access Identity Manager’s management console specific page URLs. However, the system doesn’t allow the user to carry out server side tasks without a valid web session.

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 confidence

This is an access control vulnerability in Identity Manager where unauthenticated users can directly access management console URL endpoints. While the system prevents these users from executing privileged server-side operations without a valid session, the exposure of management console interfaces to unauthenticated access constitutes an information disclosure and attack surface enlargement risk.

MitigationImplement proper authentication enforcement on all management console pages to ensure only authenticated users with valid sessions can access these endpoints. Consider IP restriction or additional access controls for sensitive administrative interfaces.

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
Symantec Identity Governance And AdministrationApplication
Affected:= 14.3= 14.4

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product version
    Use the product's version information command or check the About/Version page in the Identity Governance and Administration admin interface. Alternatively, check the installation directory for version metadata files or use the product's diagnostic tools.
    Affected if The installed version is 14.3 or 14.4 specifically, as these are the versions listed as affected by this CVE.
  2. Determine management console accessibility
    Attempt to access the Identity Manager management console URLs directly from an unauthenticated browser session (incognito/private mode) or using a HTTP client without providing credentials. Common management console paths typically include /admin, /console, or similar administrative endpoints.
    Affected if The management console or administrative interfaces load and display content without requiring a login, indicating the vulnerability is present.
  3. Verify session enforcement on admin endpoints
    Send HTTP requests to known administrative URLs without including session cookies or authentication headers. Observe whether the responses return login redirects, access denied messages, or actual administrative content.
    Affected if Administrative endpoints return actual content rather than redirecting to a login page, confirming unauthenticated access is possible.
  4. Review authentication configuration
    Examine the product's authentication configuration files (such as web.xml, application configuration, or IAM configuration settings) to verify whether authentication constraints are properly defined for management console paths.
    Affected if Authentication constraints are missing or misconfigured for management console URL patterns, allowing unauthenticated access.

A system is affected if it runs Broadcom Symantec Identity Governance and Administration version 14.3 or 14.4 AND the management console endpoints are accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication enforcement on all management console pages to ensure only authenticated users with valid sessions can access these endpoints. Consider IP restriction or additional access controls for sensitive administrative interfaces.

Fix this in Symantec Identity Governance And Administration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25626 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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