NetSight

Security Dashboard

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

Reset
146 matching advisories · page 5 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2012-1099 Cross-site Scripting in actionpack rubygems · actionpack 2012-03-13 medium4.3 CVE-2012-1098 activesupport Cross-site Scripting vulnerability rubygems · activesupport 2012-03-13 medium4.3 CVE-2011-4319 Cross-site Scripting vulnerability in i18n translations helper method rubygems · actionpack 2011-11-28 medium4.3 CVE-2011-3187 actionpack Improper Input Validation vulnerability rubygems · actionpack 2011-08-29 medium4.3 CVE-2011-3186 actionpack CRLF injection vulnerability rubygems · actionpack 2011-08-29 medium4.3 CVE-2011-2932 activesupport Cross-site Scripting vulnerability rubygems · activesupport 2011-08-29 medium4.3 CVE-2011-2931 actionpack Cross-site Scripting vulnerability rubygems · actionpack 2011-08-29 high7.5 CVE-2011-2930 activerecord vulnerable to SQL Injection rubygems · activerecord 2011-08-29 medium5.0 CVE-2011-2929 actionpack Improper Input Validation vulnerability rubygems · actionpack 2011-08-29 medium4.3 CVE-2011-2197 rails Cross-site Scripting vulnerability rubygems · actionpack, rubygems · activesupport 2011-06-30 high7.5 CVE-2011-0449 actionpack allows remote attackers to bypass intended access restrictions rubygems · actionpack 2011-02-21 high7.5 CVE-2011-0448 activerecord vulnerable to SQL Injection rubygems · activerecord 2011-02-21 medium6.8 CVE-2011-0447 actionpack Cross-Site Request Forgery vulnerability rubygems · actionpack 2011-02-14 medium4.3 CVE-2011-0446 Rails actionpack gem vulnerable to Cross-site Scripting rubygems · actionpack, rubygems · actionview 2011-02-14 medium6.4 CVE-2010-3933 Rails activerecord gem has Improper Input Validation vulnerability rubygems · activerecord 2010-10-28 medium6.8 CVE-2008-7248 Improper Input Validation in actionpack rubygems · actionpack 2009-12-16 medium4.3 CVE-2009-4214 Moderate severity vulnerability that affects rails rubygems · rails 2009-12-07 medium5.0 CVE-2009-3086 actionpack and activesupport vulnerable to information leaks rubygems · actionpack, rubygems · activesupport 2009-09-08 medium4.3 CVE-2009-3009 Cross site scripting that affects rails rubygems · actionpack, rubygems · activesupport 2009-09-08 critical9.8 CVE-2009-2422 rails vulnerable to improper authentication rubygems · rails 2009-07-10 medium5.0 CVE-2008-5189 rails is vulnerable to CRLF injection rubygems · rails 2008-11-21 high7.5 CVE-2008-4094 Rails ActiveRecord gem vulnerable to SQL injection rubygems · activerecord 2008-09-30 medium6.8 CVE-2007-6077 session fixation protection mechanism in cgi_process.rb in Rails rubygems · rails 2007-11-21 medium4.3 CVE-2007-3227 Moderate severity vulnerability that affects rails rubygems · rails 2007-06-14 high7.5 CVE-2006-4111 Ruby on Rails vulnerable to code injection rubygems · rails 2006-08-14 high7.5 CVE-2006-4112 Rails Denial of Service vulnerability rubygems · rails 2006-08-14

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.