dbcve.org
Hicos Natural Person Credential Component ClientApplication · Hinet

CVE-2022-32960

MEDIUM · 6.8 CVSS v3.1 Published 2022-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
HiCOS’ client-side citizen digital certificate component has a stack-based buffer overflow vulnerability when reading IC card due to insufficient parameter length validation for card number. An unauthenticated physical attacker can exploit this vulnerability to 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 · high confidence

HiCOS client-side citizen digital certificate component contains a stack-based buffer overflow vulnerability caused by insufficient validation of the card number parameter length when reading IC cards. An unauthenticated attacker with physical access to the system can exploit this to execute arbitrary code, manipulate data, or cause denial of service.

MitigationImplement proper bounds checking on the card number parameter before copying it to the stack buffer. Validate input length against the buffer size and use safe string handling functions.

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
Affected:= 3.0.3.30306= 3.0.3.30404= 3.1.0.00002

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
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 checks

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

  1. Identify HiCOS client installation
    Check for the presence of Hinet HiCOS Natural Person Credential Component Client on the system. Look for HiCOS-related processes, services, or installed programs. Common locations include Program Files directories or system service listings.
    Affected if The HiCOS client software is installed on the system.
  2. Determine installed HiCOS version
    Use system utility to query the installed version of the HiCOS Natural Person Credential Component Client. Check program properties, installed programs list, or version information in HiCOS-related files or registry entries.
    Affected if The installed version matches exactly 3.0.3.30306, 3.0.3.30404, or 3.1.0.00002.
  3. Verify IC card reader hardware presence
    Check if the system has an IC card reader connected or accessible. This can be done through device manager, USB device listings, or checking for smart card reader hardware interfaces.
    Affected if An IC card reader is connected and the system can communicate with it.
  4. Confirm card reading functionality is enabled
    Verify that the HiCOS client has IC card reading capabilities available. Check if the card number parameter processing feature is active within the client software.
    Affected if The IC card reading feature is available and the card number parameter can be passed to the client.

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 system has an IC card reader with card reading functionality enabled.

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 bounds checking on the card number parameter before copying it to the stack buffer. Validate input length against the buffer size and use safe string handling functions.

Fix this in Hicos Natural Person Credential Component Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32960 — 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-32960 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