CVE-2023-43297
Linecorp Line 13.6.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-43297 is a medium-severity Improper Enforcement of Message Integrity During Transmission in a Communication Channel (CWE-924) vulnerability in Linecorp Line. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Security Account Manager (T1003.002); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-47716
Vulnerability Data
An issue in animal-art-lab v13.6.1 allows attackers to send crafted notifications via leakage of the channel access token.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 1 OS baseline
—
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.
The control directly mandates integrity protection for transmitted information, addressing failures to enforce message integrity in transit.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Directly requires integrity protection (e.g., signatures/hashes) for data-in-transit, which prevents the described weakness while also addressing confidentiality/availability.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requires secure information transfer procedures that can include integrity checks.
A.8.20 explicitly requires controls to safeguard the confidentiality and integrity of data passing over networks (item e, plus hardening, filtering, protocol disabling, and virtualized separation), which directly stops exploitation of in-transit message tampering for most transmission scenarios; the bounded remainder is non-network channels or cases where the endpoint itself fails to enforce integrity checks.
A.8.21 requires identifying/implementing network service security features (auth, encryption, connection controls) plus rules for authentication, authorization, monitoring and access means (e.g. VPN); this stops exploitation of in-transit tampering for the subset of cases relying on those network-level protections, but leaves a bounded remainder where message-level integrity (e.g. signatures, MACs) is still absent or insufficient.
A.8.24's rules on algorithm selection, key management, and protecting transmitted information (esp. guidance c) directly stop modification-in-transit by mandating integrity-providing cryptography; remainder is bounded to non-crypto integrity mechanisms (e.g. non-repudiation-only schemes or physical-layer protections)
Application security requirements can specify integrity protection for transmitted messages.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (4 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-924
- V-248823 OL 8 must not have the telnet-server package installed. blocks CWE-924
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-924