CVE-2024-3281

HIGHNVD 8.88.8—

8.8

A vulnerability was discovered in the firmware builds after 8.0.2.3267 and prior to 8.1.3.1301 in CCX devices. A flaw in the firmware build process did not properly restrict access to a resource from an unauthorized actor.

CVSS v3: 8.8
EG Score: 8.8(medium)
EPSS: 52.7%
KEV: Not listed

Published

April 9, 2024

Last Modified

February 20, 2026

References (4)

hp-security-alert@hphttps://support.hp.com/us-en/document/ish_10388650-10388701-16/hpsbpy03929
hp-security-alert@hphttps://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2024-003.txt
af854a3a-2127-422b-91ae-364da2661108https://support.hp.com/us-en/document/ish_10388650-10388701-16/hpsbpy03929
af854a3a-2127-422b-91ae-364da2661108https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2024-003.txt

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-306Missing Authentication for Critical Function

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 06:09 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch

Frequently asked(5)

What is CVE-2024-3281?

CVE-2024-3281 is a high vulnerability published on April 9, 2024. A vulnerability was discovered in the firmware builds after 8.0.2.3267 and prior to 8.1.3.1301 in CCX devices. A flaw in the firmware build process did not properly restrict access to a resource from an unauthorized actor.

When was CVE-2024-3281 disclosed?

CVE-2024-3281 was first published in the National Vulnerability Database on April 9, 2024, with the most recent update on February 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-3281 actively exploited?

CVE-2024-3281 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-3281?

CVE-2024-3281 has a CVSS v3 base score of 8.8 (NVD).

How do I remediate CVE-2024-3281?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3281, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-3281

Explore →

Is Your Infrastructure Affected by CVE-2024-3281?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2024-3281

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-3281?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)