CVE-2022-2591
Published: 01 August 2022
Summary
CVE-2022-2591 is a high-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Tem Flex-1085 Firmware. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 5.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2022-2591 is a remotely exploitable denial-of-service vulnerability in TEM FLEX-1085 version 1.6.0. It resides in an unspecified function of the file /sistema/flash/reboot; crafted input to this endpoint triggers the flaw, which is tracked under CWE-404 and carries a CVSS 3.1 base score of 7.5 reflecting network attack vector, low complexity, and no required credentials or user interaction.
An unauthenticated attacker can send a malicious request over the network to the affected endpoint and cause the device to become unavailable, resulting in loss of availability with no impact on confidentiality or integrity. Public exploit code for this issue has been released.
The EPSS score has remained flat at 0.1287 with no material increase since disclosure. No vendor advisory or patch information is referenced in the available sources.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-34839
Vulnerability details
A vulnerability classified as critical has been found in TEM FLEX-1085 1.6.0. Affected is an unknown function of the file /sistema/flash/reboot. The manipulation leads to denial of service. It is possible to launch the attack remotely. The exploit has been…
more
disclosed to the public and may be used.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Contingency plan updates incorporate proper resource shutdown and release steps, preventing attackers from leveraging incomplete cleanup during recovery scenarios.
Mandates explicit shutdown of the network connection at session conclusion, directly addressing improper resource release.
Requires proper shutdown/release procedures that include overwriting or isolating data to block unintended transfer via reused system objects.
Procedures can mandate orderly shutdown or release of resources when failures occur, preventing improper resource handling after a fault.