CVE-2022-28623
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 · uneditedSecurity vulnerabilities in HPE IceWall SSO 10.0 certd could be exploited remotely to allow SQL injection or unauthorized data injection. HPE has provided the following updated modules to resolve these vulnerabilities. HPE IceWall SSO version 10.0 certd library Patch 9 for RHEL and HPE IceWall SSO version 10.0 certd library Patch 9 for HP-UX.
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 confidenceSQL injection and unauthorized data injection vulnerabilities in HPE IceWall SSO 10.0 certd library allow remote attackers to inject malicious SQL queries or manipulate data through the certd component, which handles certificate-related operations in the SSO infrastructure.
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= 10.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 if HPE IceWall SSO is installedCheck for the presence of IceWall SSO components on the system, typically installed in /opt/hp/icewall or similar HPE product directories. Look for icewall-sso or certd related directories and binaries.Affected if HPE IceWall SSO software is present on the system
-
Verify the certd library versionLocate the certd library file and check its version. On RHEL/HP-UX systems, this may be in the certd installation directory. Use commands like 'rpm -qa | grep icewall' or check the certd library file properties for version information.Affected if The installed certd version is exactly 10.0 (matches the affected version range)
-
Confirm the certd service is runningCheck if the certd service process is active. On Linux systems, use commands like 'ps aux | grep certd' or 'systemctl status certd' to determine if the certificate daemon is currently running.Affected if The certd service is active and listening for requests
-
Check network exposure of certd componentReview network configuration to determine if the certd service is exposed to network access. Use 'netstat -anp' or 'ss -tlnp' to identify listening ports associated with certd, and verify whether it is bound to external interfaces versus localhost only.Affected if The certd service is bound to external/network-accessible interfaces (not localhost only)
-
Inspect certd configuration filesExamine the certd configuration files for any non-default settings that might indicate custom SQL queries or data manipulation endpoints. Look for config files in the certd installation directory.Affected if Non-standard or custom configurations are present in certd that could be exploited
A user is affected if HPE IceWall SSO 10.0 with the certd component is installed, the certd service is running, and it is accessible over the network.
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 · scopedApply HPE IceWall SSO version 10.0 certd library Patch 9 for RHEL and HP-UX to address the SQL injection vulnerabilities; verify the certd service functions correctly and test that authentication flows remain intact after patching.
HPE IceWall SSO 10.0 with certd library Patch 9 applied
- 1. Navigate to support.hpe.com and locate HPE IceWall SSO version 10.0 certd library Patch 9
- 2. Select the appropriate patch for your platform: Patch 9 for RHEL or Patch 9 for HP-UX
- 3. Download the patch file from HPE support portal
- 4. Review the patch release notes for any prerequisites or special installation instructions
- 5. Apply the patch according to HPE's documented installation procedure for your platform
- 6. Verify the patch was applied successfully and restart the certd service if required
- 7. Test that the IceWall SSO certd functionality is working properly after the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28623 — 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-2022-28623 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