LiveActive security incident?Get immediate response
CVE Record

CVE-2019-12804: Hunesion i-oneNet Missing Support for Integrity Check vulnerability

In Hunesion i-oneNet version 3.0.7 ~ 3.0.53 and 4.0.4 ~ 4.0.16, due to the lack of update file integrity checking in the upgrade process, an attacker can craft malicious file and use it as an update.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Hunesion i-oneNet can accept update files without verifying their integrity. If a user applies a malicious update file, an attacker could compromise the system. The bundle lists versions 3.0.7 through 3.0.53 and 4.0.4 through 4.0.16 as affected. No provided source confirms active exploitation or a specific fixed version.

Executive priority

Treat as high priority for affected deployments because malicious updates can produce full system compromise, but prioritize based on whether i-oneNet is present and who can run upgrades.

Technical view

CVE-2019-12804 is a CWE-353 missing integrity-check issue in the i-oneNet upgrade process. The CVSS v3.0 vector is local, low complexity, no privileges, and requires user interaction, with high confidentiality, integrity, and availability impact. The described attack path is malicious update-file acceptance, not remote unauthenticated exploitation.

Likely exposure

Exposure is limited to organizations running Hunesion i-oneNet versions 3.0.7-3.0.53 or 4.0.4-4.0.16, especially where update files are manually handled or staged from untrusted locations.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Successful abuse requires local access context and user interaction, likely convincing someone to apply a crafted update file.

Researcher notes

Evidence is sufficient for affected version range, weakness class, and CVSS. The bundle does not provide exploit details, observed exploitation, or a named fixed version, so validation should focus on version exposure and update-chain controls.

Mitigation direction

  • Inventory Hunesion i-oneNet deployments and identify exact installed versions.
  • Check Hunesion or KRCERT/BOHO guidance for corrected versions or official remediation.
  • Only accept update files from verified vendor-controlled distribution channels.
  • Restrict upgrade privileges to trusted administrators.
  • Preserve update logs and file provenance during remediation review.

Validation and detection

  • Confirm whether installed versions fall within the affected version ranges.
  • Review upgrade procedures for any integrity or authenticity validation control.
  • Check recent update activity for unusual sources, filenames, or timing.
  • Verify administrators know not to apply untrusted update packages.
  • Document vendor guidance status, including whether a fixed release is available.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-353: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-12804 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.0HighCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.8High
CVSS 3.0 vector shape for CVE-2019-12804Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Hunesioni-oneNet3.0.7~3.0.53, 4.0.4~4.0.16Listed
Weakness

CWE details

CWE-353

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-353 · source CWE mapping

Missing Support for Integrity Check

Missing Support for Integrity Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs