CVE-2023-22291
Justsystems Ichitaro 2022 1.0.1.57600
Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-22291 is a high-severity Free of Memory not on the Heap (CWE-590) vulnerability in Justsystems Ichitaro 2022. Its CVSS base score is 7.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 38th 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-26455
Vulnerability Data
An invalid free vulnerability exists in the Frame stream parser functionality of Ichitaro 2022 1.0.1.57600. A specially crafted document can lead to an attempt to free a stack pointer, which causes memory corruption. An attacker can provide a malicious file…
more
to trigger this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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.
Secure SDLC practices directly prevent incorrect free() calls via code review, static analysis, and developer training.
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.
Secure development lifecycle mandates memory-safety practices that reduce use-after-free and invalid-free bugs.
A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, hardening, and design reviews) but does not itself stop a free() of non-heap memory from being exploitable; the weakness can still be present and reached at runtime.
Secure coding standards explicitly forbid freeing pointers not obtained from heap allocators, directly mitigating CWE-590.
Security testing in development can detect invalid-free defects before release.