BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-5660High confidence

Arm Cortex-A77 — Exposure of Resource to Wrong Sphere

Arm · Cortex-A77

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.56% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Arm Cortex-A77 and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.21v3.21 · mainarm-trusted-firmwareVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.8.32-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcearm-trusted-firmwareVendor fix publishedDebian records a fixed source-package version for this release.2.12.1+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcearm-trusted-firmwareAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcearm-trusted-firmwareVendor fix publishedDebian records a fixed source-package version for this release.2.12.1+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcearm-trusted-firmwareVendor fix publishedDebian records a fixed source-package version for this release.2.12.1+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivearm-trusted-firmwareUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-47147

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Fix not verified
01

What, why and how

Use of Hardware Page Aggregation (HPA) and Stage-1 and/or Stage-2 translation on Cortex-A77, Cortex-A78, Cortex-A78C, Cortex-A78AE, Cortex-A710, Cortex-X1, Cortex-X1C, Cortex-X2, Cortex-X3, Cortex-X4, Cortex-X925, Neoverse V1, Neoverse V2, Neoverse V3, Neoverse V3AE, Neoverse N2 may permit bypass of Stage-2 translation and/or GPT protection.

What

Use of Hardware Page Aggregation (HPA) and Stage-1 and/or Stage-2 translation on Cortex-A77, Cortex-A78, Cortex-A78C, Cortex-A78AE, Cortex-A710, Cortex-X1, Cortex-X1C, Cortex-X2, Cortex-X3, Cortex-X4, Cortex-X925, Neoverse V1, Neoverse V2, Neoverse V3, Neoverse V3AE, Neoverse N2 may permit bypass of Stage-2 translation and/or GPT protection.

Why

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Use of Hardware Page Aggregation (HPA) and Stage-1 and/or Stage-2 translation on Cortex-A77, Cortex-A78, Cortex-A78C, Cortex-A78AE, Cortex-A710, Cortex-X1, Cortex-X1C, Cortex-X2, Cortex-X3, Cortex-X4, Cortex-X925, Neoverse V1, Neoverse V2, Neoverse V3, Neoverse V3AE, Neoverse N2 may permit bypass of Stage-2 translation and/or GPT protection.

Why

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Exposure of Resource to Wrong Sphere → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-668 ↗

CWE-668: Exposure of Resource to Wrong Sphere. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-668
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0007Samsung Exynos: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Samsung Exynos ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher genannte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241211Security Bulletin 11 Dec 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Dec 2024, published on 11 December 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0151Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=CVE-2024-56597 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=CVE-2024-56598 Référence CVE CVE-2024-5660 https://www.cve.org/CVERecord?id=CVE-2024-5660 Référence CVE CVE-2024-56600 https://www.cve.org/CVERecord?id=CVE-2024-56600 Référence CVE CVE-2024-56601 https://www.cve.org/CVERecord?id=CVE-2024-56601 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0088Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-56589 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-56593 https://www.cve.org/CVERecord?id=CVE-2024-56593 Référence CVE CVE-2024-56594 https://www.cve.org/CVERecord?id=CVE-2024-56594 Référence CVE CVE-2024-56595 https://www.cve.org/CVERecord?id=CVE-2024-56595 Référence CVE CVE-2024-56596 https://www.cve.org/CVERecord?id=CVE-2024-56596 Référence CVE CVE-2024-56597 https://www.cve.org/CVERecord?id=CVE-2024-56597 Référence CVE CVE-2024-56598 https://www.cve.org/CVERecord?id=CVE-2024-56598 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-5660 https://www.cve.org/CVERecord?id=CVE-2024-5660 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-56603 https://www.cve.org/CVERecord?id=CVE-2024-56603 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56606 https://www.cve.org/CVERecord?id=CVE-2024-56606 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=C

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029775ARM Ltd.のcortex-a710 ファームウェア等の複数製品における誤った領域へのリソースの漏えいに関する脆弱性

Cortex-A77、Cortex-A78、Cortex-A78C、Cortex-A78AE、Cortex-A710、Cortex-X1、Cortex-X1C、Cortex-X2、Cortex-X3、Cortex-X4、Cortex-X925、Neoverse V1、Neoverse V2、Neoverse V3、Neoverse V3AE、Neoverse N2において、ハードウェアページ集約(HPA)およびステージ1および/またはステージ2の変換を使用すると、ステージ2の変換やGPT保護をバイパスできる可能性があります。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • Cortex-A77: version range in vendor record
  • Neoverse V1: version range in vendor record
  • Cortex-A78AE: version range in vendor record
  • Cortex-78C: version range in vendor record
  • Cortex-X1C: version range in vendor record
  • Cortex-A78: version range in vendor record
  • Cortex-X1: version range in vendor record
  • Neoverse N2: version range in vendor record
  • Cortex-A710: version range in vendor record
  • Cortex-X2: version range in vendor record
  • Neoverse V2: version range in vendor record
  • Cortex-X3: version range in vendor record
  • Neoverse V3AE: version range in vendor record
  • Neoverse V3: version range in vendor record
  • Cortex-X4: version range in vendor record
  • Cortex-X925: version range in vendor record
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Dec 2024 · Last source change 16 Dec 2024, 13:10 UTC · CWE-668 · Exposure of Resource to Wrong Sphere

CVE recordCVE.org · 5.1
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-47147
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-5660 · cve.blacktree.nl