When handling contactless cards, usage of a specific function to get additional information from the card which doesn't check the boundary on the data received while reading. This allows a stack-based buffer overflow that could lead to a potential Remote Code Execution on the tar...
Product
idemia morphowave xp firmware vulnerabilities
6 published CVES affecting idemia morphowave xp firmware, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 5
- High
- 1
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest idemia morphowave xp firmware CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 1.3%
-
CriticalCVSS 9.8 EPSS 1.0%
When reading DesFire keys, the function that reads the card isn't properly checking the boundaries when copying internally the data received. This allows a heap based buffer overflow that could lead to a potential Remote Code Execution on the targeted device. This is especially p...
-
CriticalCVSS 9.8 EPSS 1.1%
During the retrofit validation process, the firmware doesn't properly check the boundaries while copying some attributes to check. This allows a stack-based buffer overflow that could lead to a potential Remote Code Execution on the targeted device
-
CriticalCVSS 9.8 EPSS 1.1%
The handler of the retrofit validation command doesn't properly check the boundaries when performing certain validation operations. This allows a stack-based buffer overflow that could lead to a potential Remote Code Execution on the targeted device
-
CriticalCVSS 9.8 EPSS 1.1%
The Parameter Zone Read and Parameter Zone Write command handlers allow performing a Stack buffer overflow. This could potentially lead to a Remote Code execution on the targeted device.
-
HighCVSS 7.5 EPSS 0.68%
By abusing a design flaw in the firmware upgrade mechanism of the impacted terminal it's possible to cause a permanent denial of service for the terminal. the only way to recover the terminal is by sending back the terminal to the manufacturer
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.