Liman Mys
Monthly
HAVELSAN Liman MYS releases from 2.3.4-1124 up to but not including 2.3.5-1131 contain a weak forgotten-password recovery mechanism (CWE-640) that lets a network attacker abuse the account-recovery workflow to take over a targeted account, with high confidentiality and integrity impact and no effect on availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1) indicates the flaw is network-reachable and low complexity and needs no attacker credentials, but it is not fully autonomous because a victim must perform some recovery-related action (UI:R); the exact weakness in the recovery flow is not described in the available sources. No CISA KEV entry and no exploit code reference were provided, so no public exploit identified at time of analysis; TR-CERT rates it for remediation within this week.
Privilege escalation in Liman MYS (HAVELSAN Inc.) versions 2.2.3 through pre-2.3.1 enables authenticated low-privilege users to gain administrator-level access via missing server-side authorization checks (CWE-862). The platform, a centralized Linux server management system used primarily in Turkish government and enterprise environments, fails to verify whether the requesting user has rights to perform privileged operations before executing them. No public exploit identified at time of analysis, but the CVSS 8.8 score with network vector and low privilege requirement makes this a high-priority patch target for any organization running the affected versions.
Missing authorization controls in HAVELSAN Liman MYS (versions 2.2.3 through before 2.3.1) allow a low-privileged authenticated user to access and invoke functionality that should be restricted to higher-privileged roles, resulting in full confidentiality, integrity, and availability compromise of the managed system. The flaw stems from CWE-862 - the application fails to enforce ACL checks before granting access to privileged operations, effectively allowing privilege escalation within the platform. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity and network accessibility make this straightforward to exploit by any authenticated user.
Privilege escalation and unauthorized functionality access in HAVELSAN Liman MYS (Yönetim Sistemi) before release.Master.1107 allows an authenticated low-privileged user to invoke functions that should be gated by access-control lists. Because certain endpoints fail to enforce authorization (CWE-862), a limited user can reach administrative or restricted operations, enabling significant integrity and availability impact. No public exploit identified at time of analysis; the flaw was reported by Turkey's national CERT (TR-CERT / USOM).
Path traversal in HAVELSAN Liman MYS before 2.3.5-1132 allows an authenticated low-privilege user to read files outside the intended directory over the network, with high confidentiality impact and no integrity or availability impact. The CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and versions at or above 2.3.5-1132 are not affected. No CISA KEV active-exploitation signal or public exploit code was provided at time of analysis, and EPSS data was not supplied; the issue was reported by TR-CERT.
A path traversal flaw (CWE-22) in HAVELSAN Liman MYS versions 2.3.2 up to but not including 2.3.4-1124 allows remote, unauthenticated attackers to read files outside the intended web-accessible directory, resulting in limited confidentiality exposure. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3), no credentials, privileges, or user interaction are required, so any reachable instance of an affected version is directly exposed to attempts; the impact is confined to partial file disclosure with no write, integrity, or availability effect. No public exploit code was identified at the time of analysis and there is no CISA KEV listing, so exploitation is not confirmed to be active, but the low attack complexity and lack of authentication make the issue practically attractive against internet-exposed Liman MYS deployments. This is a genuine but modest-priority issue.
HAVELSAN Liman MYS releases from 2.3.4-1124 up to but not including 2.3.5-1131 contain a weak forgotten-password recovery mechanism (CWE-640) that lets a network attacker abuse the account-recovery workflow to take over a targeted account, with high confidentiality and integrity impact and no effect on availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1) indicates the flaw is network-reachable and low complexity and needs no attacker credentials, but it is not fully autonomous because a victim must perform some recovery-related action (UI:R); the exact weakness in the recovery flow is not described in the available sources. No CISA KEV entry and no exploit code reference were provided, so no public exploit identified at time of analysis; TR-CERT rates it for remediation within this week.
Privilege escalation in Liman MYS (HAVELSAN Inc.) versions 2.2.3 through pre-2.3.1 enables authenticated low-privilege users to gain administrator-level access via missing server-side authorization checks (CWE-862). The platform, a centralized Linux server management system used primarily in Turkish government and enterprise environments, fails to verify whether the requesting user has rights to perform privileged operations before executing them. No public exploit identified at time of analysis, but the CVSS 8.8 score with network vector and low privilege requirement makes this a high-priority patch target for any organization running the affected versions.
Missing authorization controls in HAVELSAN Liman MYS (versions 2.2.3 through before 2.3.1) allow a low-privileged authenticated user to access and invoke functionality that should be restricted to higher-privileged roles, resulting in full confidentiality, integrity, and availability compromise of the managed system. The flaw stems from CWE-862 - the application fails to enforce ACL checks before granting access to privileged operations, effectively allowing privilege escalation within the platform. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity and network accessibility make this straightforward to exploit by any authenticated user.
Privilege escalation and unauthorized functionality access in HAVELSAN Liman MYS (Yönetim Sistemi) before release.Master.1107 allows an authenticated low-privileged user to invoke functions that should be gated by access-control lists. Because certain endpoints fail to enforce authorization (CWE-862), a limited user can reach administrative or restricted operations, enabling significant integrity and availability impact. No public exploit identified at time of analysis; the flaw was reported by Turkey's national CERT (TR-CERT / USOM).
Path traversal in HAVELSAN Liman MYS before 2.3.5-1132 allows an authenticated low-privilege user to read files outside the intended directory over the network, with high confidentiality impact and no integrity or availability impact. The CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and versions at or above 2.3.5-1132 are not affected. No CISA KEV active-exploitation signal or public exploit code was provided at time of analysis, and EPSS data was not supplied; the issue was reported by TR-CERT.
A path traversal flaw (CWE-22) in HAVELSAN Liman MYS versions 2.3.2 up to but not including 2.3.4-1124 allows remote, unauthenticated attackers to read files outside the intended web-accessible directory, resulting in limited confidentiality exposure. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3), no credentials, privileges, or user interaction are required, so any reachable instance of an affected version is directly exposed to attempts; the impact is confined to partial file disclosure with no write, integrity, or availability effect. No public exploit code was identified at the time of analysis and there is no CISA KEV listing, so exploitation is not confirmed to be active, but the low attack complexity and lack of authentication make the issue practically attractive against internet-exposed Liman MYS deployments. This is a genuine but modest-priority issue.