NetSight

Security Dashboard

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

Reset
441 matching advisories · page 11 of 15Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.2 CVE-2021-35117 An Out of Bounds read may potentially occur while processing an IBSS beacon, in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consum… qualcomm · apq8096au_firmware, qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware +9 2022-04-01 high8.1 CVE-2022-23639 crossbeam-utils Unsoundness of AtomicCell<{i,u}64> arithmetics on 32-bit targets that support Atomic{I,U}64 rust · crossbeam-utils 2022-02-15 high7.5 CVE-2021-1981 Possible buffer over read due to improper IE size check of Bearer capability IE in MT setup request from network in Snapdragon Auto, Snapdragon Compute, Snapdr… qualcomm · apq8017_firmware, qualcomm · ar8035_firmware, qualcomm · msm8917_firmware +9 2021-11-12 high7.5 CVE-2021-30304 Possible buffer out of bound read can occur due to improper validation of TBTT count and length while parsing the beacon response in Snapdragon Compute, Snapdr… qualcomm · qca2062_firmware, qualcomm · qca2064_firmware, qualcomm · qca2065_firmware +9 2021-10-20 high7.5 CVE-2021-1980 Possible buffer over read due to lack of length check while parsing beacon IE response in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdra… qualcomm · apq8053_firmware, qualcomm · apq8064au_firmware, qualcomm · apq8096au_firmware +9 2021-10-20 high8.4 CVE-2021-30261 Possible integer and heap overflow due to lack of input command size validation while handling beacon template update command from HLOS in Snapdragon Auto, Sna… qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2021-09-17 high7.5 CVE-2021-1948 Possible out of bound read due to lack of length check of data while parsing the beacon or probe response in Snapdragon Auto, Snapdragon Compute, Snapdragon Co… qualcomm · apq8053_firmware, qualcomm · apq8064au_firmware, qualcomm · apq8096au_firmware +9 2021-09-09 high7.5 CVE-2021-34173 An attacker can cause a Denial of Service and kernel panic in v4.2 and earlier versions of Espressif esp32 via a malformed beacon csa frame. espressif · esp32_firmware 2021-07-14 high7.5 CVE-2021-1964 Possible buffer over read due to improper validation of IE size while parsing beacon from peer device in Snapdragon Auto, Snapdragon Compute, Snapdragon Connec… qualcomm · apq8053_firmware, qualcomm · aqt1000_firmware, qualcomm · ar8035_firmware +9 2021-07-13 high7.5 CVE-2021-1943 Possible buffer out of bound read can occur due to improper validation of TBTT count and length while parsing the beacon response in Snapdragon Auto, Snapdrago… qualcomm · apq8053_firmware, qualcomm · aqt1000_firmware, qualcomm · ar9380_firmware +9 2021-07-13 high8.8 CVE-2020-36406 uWebSockets 18.11.0 and 18.12.0 has a stack-based buffer overflow in uWS::TopicTree::trimTree (called from uWS::TopicTree::unsubscribeAll). uwebsockets_project · uwebsockets 2021-07-01 high8.8 CVE-2020-26516 A CSRF issue was discovered in Intland codeBeamer ALM 10.x through 10.1.SP4. intland · codebeamer 2021-06-08 high7.5 CVE-2020-26515 An insufficiently protected credentials issue was discovered in Intland codeBeamer ALM 10.x through 10.1.SP4. intland · codebeamer 2021-06-08 high7.3 CVE-2021-29242 CODESYS Control Runtime system before 3.5.17.0 has improper input validation. codesys · control_for_beaglebone_sl, codesys · control_for_empc-a\/imx6_sl, codesys · control_for_iot2000_sl +9 2021-05-03 high7.5 CVE-2021-29241 CODESYS Gateway 3 before 3.5.16.70 has a NULL pointer dereference that may result in a denial of service (DoS). codesys · control_for_beaglebone_sl, codesys · control_for_empc-a\/imx6_sl, codesys · control_for_iot2000_sl +8 2021-05-03 high7.8 CVE-2020-35455 The Taidii Diibear Android application 2.4.0 and all its derivatives allow attackers to obtain user credentials from Shared Preferences and the SQLite database… taidii · diibear 2021-03-17 high8.1 CVE-2020-36254 scp.c in Dropbear before 2020.79 mishandles the filename of . dropbear_ssh_project · dropbear_ssh 2021-02-25 high7.0 CVE-2020-17534 Improper synchronization in Apache Netbeans HTML/Java API maven · org.netbeans.html:pom 2021-01-11 high8.8 CVE-2020-26118 In SmartBear Collaborator Server through 13.3.13302, use of the Google Web Toolkit (GWT) API introduces a post-authentication Java deserialization vulnerabilit… smartbear · collaborator 2021-01-11 high8.1 CVE-2020-15254 crossbeam-channel Undefined Behavior before v0.4.4 rust · crossbeam-channel 2020-10-16 high7.5 CVE-2020-11118 u'Information exposure issues while processing IE header due to improper check of beacon IE frame' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer … qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-09-08 high7.5 CVE-2020-11115 u'Buffer over read occurs while processing information element from beacon due to lack of check of data received from beacon' in Snapdragon Auto, Snapdragon Co… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · apq8096au_firmware +9 2020-09-08 high7.5 CVE-2020-15806 CODESYS Control runtime system before 3.5.16.10 allows Uncontrolled Memory Allocation. codesys · control_for_beaglebone, codesys · control_for_empc-a\/imx6, codesys · control_for_iot2000 +9 2020-07-22 high7.5 CVE-2019-17561 Improper Verification of Cryptographic Signature in Apache Netbeans maven · org.codehaus.mevenide:netbeans 2020-03-30 high7.5 CVE-2020-8787 SuiteCRM 7.10.x versions prior to 7.10.23 and 7.11.x versions prior to 7.11.11 allow for an invalid Bean ID to be submitted. salesagility · suitecrm 2020-03-16 high7.5 CVE-2013-5687 RiskNet Acquirer before hotfix 6.0 b7+ADHOC-443 ApplicationServiceBean contains a service information disclosure. aicorporation · risknet_acquirer 2020-02-14 high7.5 CVE-2020-8815 Improper connection handling in the base connection handler in IKTeam BearFTP before v0.3.1 allows a remote attacker to achieve denial of service via a Slowlor… iktm · bearftp 2020-02-12 high7.8 CVE-2020-0697 An elevation of privilege vulnerability exists in Microsoft Office OLicenseHeartbeat task, where an attacker who successfully exploited this vulnerability coul… microsoft · office_365_proplus 2020-02-11 high7.8 CVE-2019-12180 An issue was discovered in SmartBear ReadyAPI through 2.8.2 and 3.0.0 and SoapUI through 5.5. smartbear · readyapi, smartbear · soapui 2020-02-05 high7.5 CVE-2020-8416 IKTeam BearFTP before 0.2.0 allows remote attackers to achieve denial of service via a large volume of connections to the PASV mode port. iktm · bearftp 2020-01-29

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.