Known vulnerabilities in AutoCAD LT 2023
Vendor:
Autodesk
Software:
AutoCAD LT
Version:
2023
Software CPE:
cpe:2.3:a:autodesk:autocad_lt:*:*:*:*:*:*:*:*
Website:
https://www.autodesk.com/
Total vulnerabilities:
20
Public exploits:
0
Known exploited (KEV):
0
Highest CVSSv4 Score:
8.7
Vulnerabilities by Severity
2027.1
2027.0
2024.1.8
2025.1.3
2026.1
2026
2025.1.2
2024.1.7
2024.1.6
2024.1.5
2024.1.4
2023.1.7
2023.1.6
2025.1.1
2025.1
2025
2021.1.4
2022.1.4
2023.1.5
2024.1.3
2022
2024
2023.1.4
2023.1.3
2020.1.6
2021.1.3
2020.1.3
2020.1.2
2020.1.1
2022.1.3
2023.1.1
2023.1
2023
2023.0.1
-
2019.1.4
2020.1.5
2021.1.2
2022.1.2
2019.1.3
2020.1.4
2021.1.1
2022.0.1
2019
2020
2021
2022.0
Vulnerabilities (20)
| Vulnerability | CWE-ID | CSH Severity | Public Exploit | KEV | First fixed release | Published | Bulletins |
|---|---|---|---|---|---|---|---|
| #VU107492 - Out-of-bounds write CVE-2025-1276 |
CWE-787 | High | 2023.1.7, 2024.1.7, 2025.1.2 | 16.04.2025 |
SB2025041640 |
||
| #VU107485 - Heap-based Buffer Overflow CVE-2025-1275 |
CWE-122 | High | 2023.1.7, 2024.1.7, 2025.1.2 | 16.04.2025 |
SB2025041640 |
||
| #VU88056 - Stack-based buffer overflow CVE-2024-23138 |
CWE-121 | High | 2021.1.4, 2022.1.4, 2023.1.5, 2024.1.3 | 03.04.2024 |
SB2024040310 |
||
| #VU75060 - Memory corruption CVE-2023-29067 |
CWE-119 | High | 2023.1.3 | 13.04.2023 |
SB2023041312 SB2023081709 |
||
| #VU75059 - Memory corruption CVE-2023-27915 |
CWE-119 | High | 2023.1.3 | 13.04.2023 |
SB2023041312 |
||
| #VU75058 - Stack-based buffer overflow CVE-2023-27914 |
CWE-121 | High | 2023.1.3 | 13.04.2023 |
SB2023041312 |
||
| #VU75057 - Integer overflow CVE-2023-27913 |
CWE-190 | High | 2023.1.3 | 13.04.2023 |
SB2023041312 SB2023081709 |
||
| #VU75056 - Out-of-bounds read CVE-2023-27912 |
CWE-125 | Medium | 2023.1.3 | 13.04.2023 |
SB2023041312 SB2023081709 |
||
| #VU70455 - Memory corruption CVE-2022-42940 |
CWE-119 | High | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 | 20.12.2022 |
SB2022092740 SB2022122032 SB2022122033 and 4 more |
||
| #VU70454 - Memory corruption CVE-2022-41306 |
CWE-119 | High | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 | 20.12.2022 |
SB2022092740 SB2022122032 SB2022122033 and 4 more |
||
| #VU67691 - Memory corruption CVE-2022-33890 |
CWE-119 | High | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092740 SB2022122032 SB2022122033 and 4 more |
||
| #VU67690 - Out-of-bounds write CVE-2022-33889 |
CWE-787 | High | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092740 SB2022122032 SB2022122033 and 4 more |
||
| #VU67689 - Uncaught Exception CVE-2022-33887 |
CWE-248 | Low | 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092739 |
||
| #VU67688 - Memory corruption CVE-2022-33888 |
CWE-119 | High | 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092739 |
||
| #VU67687 - Out-of-bounds write CVE-2022-33886 |
CWE-787 | High | 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092739 |
||
| #VU67686 - Out-of-bounds write CVE-2022-33885 |
CWE-787 | High | 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092739 |
||
| #VU67685 - Out-of-bounds read CVE-2022-33884 |
CWE-125 | Medium | 2022.1.3, 2023.1.1 | 27.09.2022 |
SB2022092739 |
||
| #VU65890 - Improper Link Resolution Before File Access ('Link Following') CVE-2022-33882 |
CWE-59 | Low | 2022.1.3, 2023.1.1 | 29.07.2022 |
SB2022072914 SB2022101008 |
||
| #VU65326 - Out-of-bounds read CVE-2022-33881 |
CWE-125 | High | 2023.1 | 14.07.2022 |
SB2022071424 |
||
| #VU61671 - Memory corruption CVE-2018-25032 |
CWE-119 | Medium | 2022.1.3, 2023.1.1 | 28.03.2022 |
SB2022032844 SB2022032845 SB2022033018 and 192 more |