Health Insurance Web Service ComponentApplication · Nhi

CVE-2022-35217

HIGH · 7.8 CVSS v3.1 Published 2022-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
The NHI card’s web service component has a stack-based buffer overflow vulnerability due to insufficient validation for network packet header length. A local area network attacker with general user privilege can exploit this vulnerability to execute arbitrary code, manipulate system command or disrupt 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 confidence

The NHI card's web service component contains a stack-based buffer overflow vulnerability caused by insufficient validation of network packet header length. A local area network attacker with general user privileges can exploit this to execute arbitrary code, manipulate system commands, or cause service disruption.

MitigationApply vendor-provided security patches for the NHI card web service component. If patches are unavailable, implement network segmentation to restrict LAN access and add input validation for packet header length processing as a compensating control.

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
Health Insurance Web Service ComponentApplication
Affected:all versions

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Identify NHI Health Insurance Web Service Component
    Inventory installed software on systems or check running services for the NHI card web service component. On Windows, review installed programs list or running services. On Linux, check process lists or installed packages for terms like 'nhi', 'health insurance', 'web service', or related naming.
    Affected if The NHI Health Insurance Web Service Component is present on the system regardless of version, as all versions are affected.
  2. Verify web service is network accessible
    Check network configuration to determine if the NHI web service component is bound to network interfaces accessible from the local area network. Use netstat or equivalent commands to identify listening ports and their binding addresses.
    Affected if The NHI web service component listens on interfaces reachable from the LAN, enabling a LAN attacker to send malicious packets.
  3. Confirm attacker has LAN access
    Review network segmentation and access control policies. Determine if general user accounts can access the network segment where the NHI web service component is deployed.
    Affected if General users without elevated privileges can reach the NHI web service component over the LAN.
  4. Check if packet header validation is disabled
    Review configuration files or registry settings related to the NHI web service component for any input validation or packet header length validation settings. Examine logs for any indicators of malformed packet handling.
    Affected if Packet header length validation is not enforced or can be bypassed in the configuration.

The environment is affected if the NHI Health Insurance Web Service Component is present and accessible from the LAN, as all versions contain the buffer overflow vulnerability.

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

Apply vendor-provided security patches for the NHI card web service component. If patches are unavailable, implement network segmentation to restrict LAN access and add input validation for packet header length processing as a compensating control.

Fix this in Health Insurance Web Service Component Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35217 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