NVD / CVE Program· CNA CERTVDE

CVE-2024-24781: Hima: Uncontrolled Resource Consumption in multiple products

HighCVSS 7.5 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 54.2% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An unauthenticated remote attacker can use an uncontrolled resource consumption vulnerability to DoS the affected devices through excessive traffic on a single ethernet port.

Published: Feb 13, 2024
Updated: Jun 17, 2026
EPSS: 0.7% · 54th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · CERTVDE: 7.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
hima	f30 03x yy \(com\) firmware	cpe:2.3:o:hima:f30_03x_yy_\(com\)_firmware
hima	f30 03x yy \(com\)	cpe:2.3:h:hima:f30_03x_yy_\(com\)
hima	f30 03x yy \(cpu\) firmware	cpe:2.3:o:hima:f30_03x_yy_\(cpu\)_firmware
hima	f30 03x \(cpu\) yy	cpe:2.3:h:hima:f30_03x_\(cpu\)_yy
hima	f35 03x yy \(com\) firmware	cpe:2.3:o:hima:f35_03x_yy_\(com\)_firmware
hima	f35 03x yy \(com\)	cpe:2.3:h:hima:f35_03x_yy_\(com\)_
hima	f35 03x yy \(cpu\) firmware	cpe:2.3:o:hima:f35_03x_yy_\(cpu\)_firmware
hima	f35 03x yy \(cpu\)	cpe:2.3:h:hima:f35_03x_yy_\(cpu\)
hima	f60 cpu 03x yy \(com\) firmware	cpe:2.3:o:hima:f60_cpu_03x_yy_\(com\)_firmware
hima	f60 cpu 03x yy \(com\)	cpe:2.3:h:hima:f60_cpu_03x_yy_\(com\)
hima	f60 cpu 03x yy \(cpu\) firmware	cpe:2.3:o:hima:f60_cpu_03x_yy_\(cpu\)_firmware
hima	f60 cpu 03x yy \(cpu\)	cpe:2.3:h:hima:f60_cpu_03x_yy_\(cpu\)

and 14 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.

HIMA F-COM 01
- up to and including 14.12affected · semver
HIMA F-COM 01 coated
- up to and including 14.12affected · semver
HIMA F-CPU 01
- up to and including 14.6affected · semver
HIMA F-CPU 01 coated
- up to and including 14.6affected · semver
HIMA F30 03X YY (COM)
- up to and including 24.14affected · semver
HIMA F30 03X YY (CPU)
- up to and including 18.6affected · semver
HIMA F35 03X YY (COM)
- up to and including 24.14affected · semver
HIMA F35 03X YY (CPU)
- up to and including 18.6affected · semver
HIMA F60 CPU 03X YY (COM)
- up to and including 24.14affected · semver
HIMA F60 CPU 03X YY (CPU)
- up to and including 18.6affected · semver
HIMA X-COM 01 E YY
- up to and including 15.14affected · semver
HIMA X-COM 01 YY
- up to and including 14.12affected · semver

Affected versions · NVD (13)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

hima f-com 01 firmwareup to 14.12 inclusive
hima f-cpu 01 firmwareup to 14.16 inclusive
hima f30 03x yy (com) firmwareup to 24.14 inclusive
hima f30 03x yy (cpu) firmwareup to 18.6 inclusive
hima f35 03x yy (com) firmwareup to 24.14 inclusive
hima f35 03x yy (cpu) firmwareup to 18.6 inclusive
hima f60 cpu 03x yy (com) firmwareup to 24.14 inclusive
hima f60 cpu 03x yy (cpu) firmwareup to 18.6 inclusive
hima x-com 01 e yy firmwareup to 15.14 inclusive
hima x-com 01 yy firmwareup to 14.12 inclusive
hima x-cpu 01 firmwareup to 14.16 inclusive
hima x-cpu 31 firmwareup to 14.16 inclusive
hima x-sb 01 firmwareup to 7.54 inclusive

Same product

hima: all records

Other highest-scoring records for the same primary product.

CVE-2024-24782HIMA: Origin Validation Error in multiple products
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

cert.vde.com/en/advisories/VDE-2024-013

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records