Liman Render Engine
Monthly
Improper TLS certificate validation in HAVELSAN Liman Render Engine (versions from 1.0 up to but not including 1.2-75) lets a network-positioned adversary conduct an adversary-in-the-middle attack, causing the engine to accept forged or otherwise invalid certificates so that intercepted traffic can be decrypted and sensitive data disclosed. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, base 5.9) shows no authentication or user-interaction prerequisite, but exploitation hinges on the attacker first occupying a man-in-the-middle position on the path between an engine endpoint and its peer, which is why the attack is scored high-complexity and the impact is confidentiality-only with no integrity or availability effect. No public exploit code has been identified at time of analysis, CISA SSVC records exploitation as 'none' with automatable 'no' and partial technical impact, and the issue was reported by TR-CERT.
Interception of the key exchange in HAVELSAN Liman Render Engine (versions 1.0 up to but not including 1.2-75) allows an on-path attacker to decrypt or meddle with traffic, because keys are agreed without authenticating the peer entity (CWE-322). Exploitation requires the attacker to already hold a position on the network path between the victim client and the Render Engine - through ARP spoofing, a rogue access point, or a compromised router - which is why the issue carries HIGH attack complexity even though no credentials (PR:N) and no user interaction (UI:N) are needed. The impact is confined to confidentiality (CVSS 3.1 base 5.9, C:H/I:N/A:N); no public exploit code and no active exploitation have been identified at time of analysis, and the CISA SSVC assessment rates exploitation as none, automatable as no, and technical impact as partial, making this a moderate, situational risk rather than a broad-exploitation priority.
Improper TLS certificate validation in HAVELSAN Liman Render Engine (versions from 1.0 up to but not including 1.2-75) lets a network-positioned adversary conduct an adversary-in-the-middle attack, causing the engine to accept forged or otherwise invalid certificates so that intercepted traffic can be decrypted and sensitive data disclosed. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, base 5.9) shows no authentication or user-interaction prerequisite, but exploitation hinges on the attacker first occupying a man-in-the-middle position on the path between an engine endpoint and its peer, which is why the attack is scored high-complexity and the impact is confidentiality-only with no integrity or availability effect. No public exploit code has been identified at time of analysis, CISA SSVC records exploitation as 'none' with automatable 'no' and partial technical impact, and the issue was reported by TR-CERT.
Interception of the key exchange in HAVELSAN Liman Render Engine (versions 1.0 up to but not including 1.2-75) allows an on-path attacker to decrypt or meddle with traffic, because keys are agreed without authenticating the peer entity (CWE-322). Exploitation requires the attacker to already hold a position on the network path between the victim client and the Render Engine - through ARP spoofing, a rogue access point, or a compromised router - which is why the issue carries HIGH attack complexity even though no credentials (PR:N) and no user interaction (UI:N) are needed. The impact is confined to confidentiality (CVSS 3.1 base 5.9, C:H/I:N/A:N); no public exploit code and no active exploitation have been identified at time of analysis, and the CISA SSVC assessment rates exploitation as none, automatable as no, and technical impact as partial, making this a moderate, situational risk rather than a broad-exploitation priority.