Hicos Natural Person Credential Component ClientApplication · Hinet
CVE-2022-32962
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 · uneditedHiCOS’ client-side citizen certificate component has a double free vulnerability. An unauthenticated physical attacker can exploit this vulnerability to corrupt memory and execute arbitrary code, manipulate system data or terminate service.
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 confidenceThe HiCOS client-side citizen certificate component contains a double free vulnerability where memory is freed twice, leading to heap corruption. An unauthenticated attacker with physical access can exploit this to execute arbitrary code, manipulate system data, or cause denial of service.
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
Hicos Natural Person Credential Component ClientApplication
= 3.0.3.30306= 3.0.3.30404= 3.1.0.00002CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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.
-
Check if HiCOS client is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programsAffected if HiCOS Natural Person Credential Component Client appears in the installed programs list
-
Identify installed HiCOS versionIn Programs and Features, locate the HiCOS entry and note the version column, or check the executable properties of the HiCOS installation folder typically found in C:\Program Files\HiCOS\ or C:\Program Files (x86)\HiCOS\Affected if The displayed version matches 3.0.3.30306, 3.0.3.30404, or 3.1.0.00002 exactly
-
Verify HiCOS service or process is activeOpen Task Manager and look for hicos*.exe processes, or run 'Get-Process | Where-Object {$_.ProcessName -like "*hicos*"}' in PowerShellAffected if A HiCOS-related process is running on the system
-
Check HiCOS driver component statusRun 'sc query hicos' in Command Prompt to check if the HiCOS service is registered, or view services via Services.msc for a service related to HiCOSAffected if A HiCOS service or driver is registered and running on the system
A user is affected if the HiCOS Natural Person Credential Component Client is installed with version 3.0.3.30306, 3.0.3.30404, or 3.1.0.00002 and the component is active on the system.
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 dataApply vendor patches from HiCOS for the citizen certificate client component; verify the patch addresses the double free in memory management routines.
Fix this in Hicos Natural Person Credential Component Client
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32962 — 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-32962 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