NetSight

Security Dashboard

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

Reset
409 matching advisories · page 13 of 14Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2021-27040 A maliciously crafted DWG file can be forced to read beyond allocated boundaries when parsing the DWG file. autodesk · advance_steel, autodesk · autocad, autodesk · autocad_architecture +9 2021-06-25 high7.8 CVE-2021-27032 Autodesk Licensing Installer was found to be vulnerable to privilege escalation issues. autodesk · licensing_services 2021-05-28 high7.8 CVE-2021-27031 A user may be tricked into opening a malicious FBX file which may exploit a use-after-free vulnerability in FBX's Review causing the application to reference a… autodesk · fbx_review 2021-04-19 high7.8 CVE-2021-27030 A user may be tricked into opening a malicious FBX file which may exploit a Directory Traversal Remote Code Execution vulnerability in FBX’s Review causing it … autodesk · fbx_review 2021-04-19 medium5.5 CVE-2021-27029 The user may be tricked into opening a malicious FBX file which may exploit a Null Pointer Dereference vulnerability in FBX's Review version 1.5.0 and prior ca… autodesk · fbx_review 2021-04-19 high7.8 CVE-2021-27028 A Memory Corruption Vulnerability in Autodesk FBX Review version 1.5.0 and prior may lead to remote code execution through maliciously crafted DLL files. autodesk · fbx_review 2021-04-19 high7.8 CVE-2021-27027 An Out-Of-Bounds Read Vulnerability in Autodesk FBX Review version 1.5.0 and prior may lead to code execution through maliciously crafted DLL files or informat… autodesk · fbx_review 2021-04-19 low3.3 CVE-2021-27596 When a user opens manipulated Autodesk 3D Studio for MS-DOS (.3DS) files received from untrusted sources in SAP 3D Visual Enterprise Viewer, the application cr… sap · 3d_visual_enterprise_viewer 2021-03-22 high7.8 CVE-2020-7085 A heap overflow vulnerability in the Autodesk FBX-SDK versions 2019.2 and earlier may lead to arbitrary code execution on a system running it. autodesk · fbx_software_development_kit 2020-04-17 medium5.5 CVE-2020-7084 A NULL pointer dereference vulnerability in the Autodesk FBX-SDK versions 2019.0 and earlier may lead to denial of service of the application. autodesk · fbx_software_development_kit 2020-04-17 medium6.5 CVE-2020-7083 An intager overflow vulnerability in the Autodesk FBX-SDK versions 2019.0 and earlier may lead to denial of service of the application. autodesk · fbx_software_development_kit 2020-04-17 high8.8 CVE-2020-7082 A use-after-free vulnerability in the Autodesk FBX-SDK versions 2019.0 and earlier may lead to code execution on a system running it. autodesk · fbx_software_development_kit 2020-04-17 high8.8 CVE-2020-7081 A type confusion vulnerability in the Autodesk FBX-SDK versions 2019.0 and earlier may lead to arbitary code read/write on the system running it. autodesk · fbx_software_development_kit 2020-04-17 high7.8 CVE-2020-7080 A buffer overflow vulnerability in the Autodesk FBX-SDK versions 2019.0 and earlier may lead to arbitrary code execution on a system running it. autodesk · fbx_software_development_kit 2020-04-17 high7.8 CVE-2020-7079 An improper signature validation vulnerability in Autodesk Dynamo BIM versions 2.5.1 and 2.5.0 may lead to code execution through maliciously crafted DLL files. autodesk · dynamo_bim 2020-04-17 high7.8 CVE-2019-7366 Buffer overflow vulnerability in Autodesk FBX Software Development Kit version 2019.5. autodesk · fbx_software_development_kit 2019-12-03 high7.8 CVE-2019-7365 DLL preloading vulnerability in Autodesk Desktop Application versions 7.0.16.29 and earlier. autodesk · autodesk_desktop 2019-12-03 high7.8 CVE-2019-7363 Use-after-free vulnerability in Autodesk Design Review versions 2011, 2012, 2013, and 2018. autodesk · design_review 2019-08-23 high7.8 CVE-2019-7362 DLL preloading vulnerability in Autodesk Design Review versions 2011, 2012, 2013, and 2018. autodesk · design_review 2019-08-23 high7.8 CVE-2019-7364 DLL preloading vulnerability in versions 2017, 2018, 2019, and 2020 of Autodesk Advanced Steel, Civil 3D, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD El… autodesk · advance_steel, autodesk · autocad, autodesk · autocad_architecture +9 2019-08-23 high7.8 CVE-2019-7361 An attacker may convince a victim to open a malicious action micro (.actm) file that has serialized data, which may trigger a code execution in Autodesk Advanc… autodesk · advance_steel, autodesk · autocad, autodesk · autocad_architecture +8 2019-04-09 high7.8 CVE-2019-7360 An exploitable use-after-free vulnerability in the DXF-parsing functionality in Autodesk Advance Steel 2018, Autodesk AutoCAD 2018, Autodesk AutoCAD Architectu… autodesk · advance_steel, autodesk · autocad, autodesk · autocad_architecture +8 2019-04-09 high7.8 CVE-2019-7359 An exploitable heap overflow vulnerability in the AcCellMargin handling code in Autodesk Advance Steel 2018, Autodesk AutoCAD 2018, Autodesk AutoCAD Architectu… autodesk · advance_steel, autodesk · autocad, autodesk · autocad_architecture +8 2019-04-09 high7.8 CVE-2019-7358 An exploitable heap overflow vulnerability in the DXF-parsing functionality in Autodesk Advance Steel 2018, Autodesk AutoCAD 2018, Autodesk AutoCAD Architectur… autodesk · advance_steel, autodesk · autocad, autodesk · autocad_architecture +8 2019-04-09 critical9.8 CVE-2016-9307 Multiple buffer overflows in the Autodesk FBX-SDK before 2017.1 can allow attackers to execute arbitrary code when reading or converting malformed 3DS format f… autodesk · fbx_software_development_kit 2017-01-25 critical9.8 CVE-2016-9306 Multiple buffer overflows in the Autodesk FBX-SDK before 2017.1 can allow attackers to execute arbitrary code when reading or converting malformed DAE format f… autodesk · fbx_software_development_kit 2017-01-25 critical9.8 CVE-2016-9305 Improper handling in the Autodesk FBX-SDK before 2017.1 of type mismatches and previously deleted objects related to reading and converting malformed FBX forma… autodesk · fbx_software_development_kit 2017-01-25 high8.8 CVE-2016-9304 Multiple buffer overflows in the Autodesk FBX-SDK before 2017.1 can allow attackers to execute arbitrary code when reading or converting malformed DFX format f… autodesk · fbx_software_development_kit 2017-01-25 critical9.8 CVE-2016-9303 Multiple buffer overflows in the Autodesk FBX-SDK before 2017.1 can allow attackers to execute arbitrary code or cause an infinite loop condition when reading … autodesk · fbx_software_development_kit 2017-01-25 high7.5 CVE-2016-2344 Stack-based buffer overflow in manager.exe in Backburner Manager in Autodesk Backburner 2016 2016.0.0.2150 and earlier allows remote attackers to execute arbit… autodesk · autodesk_backburner 2016-03-28

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.