NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
409 matching advisories · page 9 of 14Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2023-29075 A maliciously crafted PRT file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause an Out-Of-Bounds Write. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +7 2023-11-23 high7.8 CVE-2023-41140 A maliciously crafted PRT file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause a Heap-Based Buffer Overflow. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +8 2023-11-23 critical9.8 CVE-2023-29074 A maliciously crafted CATPART file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause an Out-Of-Bounds Write. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +8 2023-11-23 critical9.8 CVE-2023-29073 A maliciously crafted MODEL file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause a Heap-Based Buffer Overflow. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +8 2023-11-23 medium4.3 CVE-2023-41146 Autodesk Customer Support Portal allows cases created by users under an account to see cases created by other users on the same account. autodesk · customer_portal 2023-11-22 medium5.3 CVE-2023-41145 Autodesk users who no longer have an active license for an account can still access cases for that account. autodesk · customer_portal 2023-11-22 high7.8 CVE-2023-29069 A maliciously crafted DLL file can be forced to install onto a non-default location, and attacker can overwrite parts of the product with malicious DLLs. autodesk · desktop_connector 2023-11-22 high7.8 CVE-2023-25002 A maliciously crafted SKP file in Autodesk products is used to trigger use-after-free vulnerability. autodesk · 3ds_max, autodesk · navisworks, autodesk · revit +1 2023-06-27 high7.8 CVE-2023-25001 A maliciously crafted SKP file in Autodesk Navisworks 2023 and 2022 be used to trigger use-after-free vulnerability. autodesk · navisworks 2023-06-27 high7.8 CVE-2023-29068 A maliciously crafted file consumed through pskernel.dll file could lead to memory corruption vulnerabilities. autodesk · alias, autodesk · autocad, autodesk · autocad_advance_steel +9 2023-06-27 high7.8 CVE-2023-25004 A maliciously crafted pskernel.dll file in Autodesk products is used to trigger integer overflow vulnerabilities. autodesk · alias, autodesk · autocad, autodesk · autocad_advance_steel +9 2023-06-27 high7.8 CVE-2023-27908 A maliciously crafted DLL file can be forced to write beyond allocated boundaries in the Autodesk installer when parsing the DLL files and could lead to a Priv… autodesk · installer 2023-06-23 high7.8 CVE-2023-25003 A maliciously crafted pskernel.dll file in Autodesk AutoCAD 2023 and Maya 2022 may be used to trigger out-of-bound read write / read vulnerabilities. autodesk · alias, autodesk · autocad, autodesk · autocad_advance_steel +9 2023-06-23 high7.8 CVE-2023-25009 A malicious actor may convince a user to open a malicious USD file that may trigger an out-of-bounds write vulnerability which could result in code execution. autodesk · 3ds_max_usd 2023-05-12 high7.8 CVE-2023-25008 A malicious actor may convince a user to open a malicious USD file that may trigger an out-of-bounds read vulnerability which could result in code execution. autodesk · 3ds_max_usd 2023-05-12 high7.8 CVE-2023-25007 A malicious actor may convince a user to open a malicious USD file that may trigger an uninitialized pointer which could result in code execution. autodesk · 3ds_max_usd 2023-05-12 high7.8 CVE-2023-25006 A malicious actor may convince a user to open a malicious USD file that may trigger a use-after-free vulnerability which could result in code execution. autodesk · 3ds_max_usd 2023-05-12 high7.8 CVE-2023-25005 A maliciously crafted DLL file can be forced to read beyond allocated boundaries in Autodesk InfraWorks 2023, and 2021 when parsing the DLL files could lead to… autodesk · infraworks 2023-05-12 high7.8 CVE-2023-27911 A user may be tricked into opening a malicious FBX file that may exploit a heap buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may lea… autodesk · fbx_software_development_kit 2023-04-17 high7.8 CVE-2023-27910 A user may be tricked into opening a malicious FBX file that may exploit a stack buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may le… autodesk · fbx_software_development_kit 2023-04-17 high7.8 CVE-2023-27909 An Out-Of-Bounds Write Vulnerability in Autodesk® FBX® SDK version 2020 or prior may lead to code execution through maliciously crafted FBX files or informatio… autodesk · fbx_software_development_kit 2023-04-17 high7.8 CVE-2023-27907 A malicious actor may convince a victim to open a malicious USD file that may trigger an out-of-bounds write vulnerability which may result in code execution. autodesk · maya_usd 2023-04-17 high7.8 CVE-2023-27906 A malicious actor may convince a victim to open a malicious USD file that may trigger an out-of-bounds read vulnerability which may result in code execution. autodesk · maya_usd 2023-04-17 high7.8 CVE-2023-25010 A malicious actor may convince a victim to open a malicious USD file that may trigger an uninitialized variable which may result in code execution. autodesk · maya_usd 2023-04-17 high7.8 CVE-2023-29067 A maliciously crafted X_B file when parsed through Autodesk® AutoCAD® 2023 could lead to memory corruption vulnerability by write access violation. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +7 2023-04-14 high7.8 CVE-2023-27915 A maliciously crafted X_B file when parsed through Autodesk® AutoCAD® 2023 could lead to memory corruption vulnerability by read access violation. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +7 2023-04-14 high7.8 CVE-2023-27914 A maliciously crafted X_B file when parsed through Autodesk® AutoCAD® 2023 can be used to write beyond the allocated buffer causing a Stack Buffer Overflow. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +7 2023-04-14 high7.8 CVE-2023-27913 A maliciously crafted X_B file when parsed through Autodesk® AutoCAD® 2023 can be used to cause an Integer Overflow. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +7 2023-04-14 high7.8 CVE-2023-27912 A maliciously crafted X_B file when parsed through Autodesk® AutoCAD® 2023 can force an Out-of-Bound Read. autodesk · autocad, autodesk · autocad_advance_steel, autodesk · autocad_architecture +7 2023-04-14 high7.8 CVE-2022-42947 A maliciously crafted X_B file when parsed through Autodesk Maya 2023 and 2022 can be used to write beyond the allocated buffer. autodesk · maya 2022-12-19

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.