CVE-2023-49100

MEDIUMNVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

Score 4.4 from GitHub Security Advisory published 2024-02-21. NVD baseline CVSS 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Trusted Firmware-A (TF-A) before 2.10 has a potential read out-of-bounds in the SDEI service. The input parameter passed in register x1 is not validated well enough in the function sdei_interrupt_bind. The parameter is passed to a call to plat_ic_get_interrupt_type. It can be any arbitrary value passing checks in the function plat_ic_is_sgi. A compromised Normal World (Linux kernel) can enable a root-privileged attacker to issue arbitrary SMC calls. Using this primitive, he can control the content of registers x0 through x6, which are used to send parameters to TF-A. Out-of-bounds addresses can be read in the context of TF-A (EL3). Because the read value is never returned to non-secure memory or in registers, no leak is possible. An attacker can still crash TF-A, however.

CVSS v3
4.4
EG Score
4.4(medium)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

February 21, 2024

Last Modified

April 15, 2026

References (6)

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware—2.8.14-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware—2.8.14-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware—2.8.14-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware2.10.0+dfsg-1 ... 2.9.0+dfsg-3 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware2.10.0+dfsg-1 ... 2.9.0+dfsg-3 (9 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware—2.10.0+dfsg-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
arm-trusted-firmware—2.10.0+dfsg-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-09-24 14:01 UTCEPSS rescore
  2. 2026-09-24 14:01 UTCEPSS rescore
  3. 2026-09-23 13:46 UTCEPSS rescore
  4. 2026-09-22 14:46 UTCEPSS rescore
  5. 2026-09-21 20:31 UTCEPSS rescore
  6. 2026-09-20 20:14 UTCEPSS rescore
  7. 2026-09-20 20:14 UTCEPSS rescore
  8. 2026-09-18 19:26 UTCEPSS rescore
  9. 2026-09-17 22:50 UTCOSV refresh
  10. 2026-09-17 19:25 UTCEPSS rescore
  11. 2026-09-16 14:06 UTCEPSS rescore
  12. 2026-09-16 05:11 UTCEPSS rescore
  13. 2026-09-15 03:08 UTCEPSS rescore
  14. 2026-09-13 16:44 UTCEPSS rescore
  15. 2026-09-12 14:58 UTCEPSS rescore
  16. 2026-09-11 14:50 UTCEPSS rescore
  17. 2026-09-11 09:34 UTCEPSS rescore
  18. 2026-09-08 21:58 UTCEPSS rescore
  19. 2026-09-07 15:59 UTCEPSS rescore
  20. 2026-09-06 13:46 UTCEPSS rescore
  21. 2026-09-06 13:45 UTCEPSS rescore
  22. 2026-09-05 15:26 UTCEPSS rescore
  23. 2026-09-04 13:58 UTCEPSS rescore
  24. 2026-09-04 05:04 UTCEPSS rescore
  25. 2026-09-02 14:10 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:09 UTCEPSS rescore
  2. 2026-09-01 13:51 UTCEPSS rescore
  3. 2026-09-01 04:35 UTCEPSS rescore
  4. 2026-08-30 19:15 UTCEPSS rescore
  5. 2026-08-30 01:20 UTCEPSS rescore
  6. 2026-08-29 22:43 UTCOSV refresh
  7. 2026-08-28 21:39 UTCEPSS rescore
  8. 2026-08-27 14:23 UTCEPSS rescore
  9. 2026-08-26 14:44 UTCEPSS rescore
  10. 2026-08-25 13:46 UTCEPSS rescore
  11. 2026-08-24 14:14 UTCEPSS rescore
  12. 2026-08-23 00:17 UTCEPSS rescore
  13. 2026-08-21 23:47 UTCEPSS rescore
  14. 2026-08-20 22:53 UTCEPSS rescore
  15. 2026-08-19 17:02 UTCEPSS rescore
  16. 2026-08-19 17:02 UTCEPSS rescore
  17. 2026-08-18 13:46 UTCEPSS rescore
  18. 2026-08-17 13:45 UTCEPSS rescore
  19. 2026-08-16 14:54 UTCEPSS rescore
  20. 2026-08-16 02:12 UTCEPSS rescore
  21. 2026-08-15 01:28 UTCEPSS rescore
  22. 2026-08-13 21:58 UTCEPSS rescore
  23. 2026-08-13 09:14 UTCOSV refresh
  24. 2026-08-12 13:49 UTCEPSS rescore
  25. 2026-08-11 13:40 UTCEPSS rescore
  26. 2026-08-10 23:57 UTCEPSS rescore
  27. 2026-08-09 13:44 UTCEPSS rescore
  28. 2026-08-09 13:44 UTCEPSS rescore
  29. 2026-08-08 16:35 UTCEPSS rescore
  30. 2026-08-07 16:25 UTCEPSS rescore
  31. 2026-08-06 13:45 UTCEPSS rescore
  32. 2026-08-05 19:15 UTCEPSS rescore
  33. 2026-08-04 15:07 UTCEPSS rescore
  34. 2026-08-04 10:35 UTCEPSS rescore
  35. 2026-08-03 10:34 UTCEPSS rescore
  36. 2026-08-03 10:34 UTCEPSS rescore
  37. 2026-08-02 02:25 UTCEPSS rescore
  38. 2026-08-02 02:25 UTCEPSS rescore
  39. 2026-08-01 04:14 UTCEPSS rescore
  40. 2026-07-30 16:26 UTCEPSS rescore
  41. 2026-07-30 16:26 UTCEPSS rescore
  42. 2026-07-30 01:28 UTCEPSS rescore
  43. 2026-07-28 17:59 UTCOSV refresh
  44. 2026-07-28 15:34 UTCEPSS rescore
  45. 2026-07-28 15:34 UTCEPSS rescore
  46. 2026-07-27 14:10 UTCEPSS rescore
  47. 2026-07-26 14:52 UTCEPSS rescore
  48. 2026-07-25 14:16 UTCEPSS rescore
  49. 2026-07-24 14:16 UTCEPSS rescore
  50. 2026-07-24 14:16 UTCEPSS rescore
  51. 2026-07-23 14:16 UTCEPSS rescore
  52. 2026-07-23 02:28 UTCEG score recompute
  53. 2026-07-22 23:14 UTCEG score recompute
  54. 2026-07-22 14:06 UTCEPSS rescore
  55. 2026-07-21 15:23 UTCEPSS rescore
  56. 2026-07-21 15:23 UTCEPSS rescore
  57. 2026-07-20 17:06 UTCEPSS rescore
  58. 2026-07-19 14:29 UTCEPSS rescore
  59. 2026-07-19 14:29 UTCEPSS rescore
  60. 2026-07-19 02:27 UTCEPSS rescore
  61. 2026-07-18 10:03 UTCEPSS rescore
  62. 2026-07-18 10:03 UTCEPSS rescore
  63. 2026-07-16 17:01 UTCEPSS rescore
  64. 2026-07-15 16:56 UTCEPSS rescore
  65. 2026-07-15 16:56 UTCEPSS rescore
  66. 2026-07-15 01:59 UTCEPSS rescore
  67. 2026-07-15 01:59 UTCEPSS rescore
  68. 2026-07-13 22:28 UTCEPSS rescore
  69. 2026-07-13 22:28 UTCEPSS rescore
  70. 2026-07-13 06:11 UTCEPSS rescore
  71. 2026-07-13 06:11 UTCEPSS rescore
  72. 2026-07-12 05:45 UTCEPSS rescore
  73. 2026-07-11 10:11 UTCOSV refresh
  74. 2026-07-11 08:26 UTCEPSS rescore
  75. 2026-07-09 19:08 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-49100?
CVE-2023-49100 is a medium vulnerability published on February 21, 2024. Trusted Firmware-A (TF-A) before 2.10 has a potential read out-of-bounds in the SDEI service. The input parameter passed in register x1 is not validated well enough in the function sdeiinterruptbind. The parameter is passed to a call to platicgetinterrupttype. It can be any arbitrary value passing…
When was CVE-2023-49100 disclosed?
CVE-2023-49100 was first published in the National Vulnerability Database on February 21, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-49100 actively exploited?
CVE-2023-49100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.4% of all scored CVEs.
What is the CVSS score of CVE-2023-49100?
CVE-2023-49100 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2023-49100?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-49100, 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-2023-49100

Explore →

Is Your Infrastructure Affected by CVE-2023-49100?

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

Book a Demo →Browse All CVEs