NetSight

Security Dashboard

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

Reset
48 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2016-2169 Cloud Foundry Cloud Controller, capi-release versions prior to 1.0.0 and cf-release versions prior to v237, contain a business logic flaw. cloudfoundry · capi-release, cloudfoundry · cf-release 2018-04-18 medium6.1 CVE-2018-1190 Pivotal Cloud Foundry UAA XSS on UAA OpenID Connect check session iframe endpoint maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2018-01-04 medium6.5 CVE-2017-14389 An issue was discovered in Cloud Foundry Foundation capi-release (all versions prior to 1.45.0), cf-release (all versions prior to v280), and cf-deployment (al… cloudfoundry · capi-release, cloudfoundry · cf-deployment, cloudfoundry · cf-release 2017-11-28 medium5.3 CVE-2017-8031 Cloud Foundry UAA Denial of Service through client token revocation endpoint maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-11-27 medium6.1 CVE-2017-8047 In Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274, in some applications, it is possible to appen… cloudfoundry · cf-release, pivotal · routing-release 2017-10-04 medium4.7 CVE-2016-0713 Gorouter in Cloud Foundry cf-release v141 through v228 allows man-in-the-middle attackers to conduct cross-site scripting (XSS) attacks via vectors related to … cloudfoundry · cf-release 2017-08-31 medium6.6 CVE-2017-8034 The Cloud Controller and Router in Cloud Foundry (CAPI-release capi versions prior to v1.32.0, Routing-release versions prior to v0.159.0, CF-release versions … cloudfoundry · capi-release, cloudfoundry · cf-release, cloudfoundry · routing-release 2017-07-17 medium6.6 CVE-2017-8032 Cloud Foundry UAA Identity Zone Admin Privilege Escalation maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-07-10 medium6.5 CVE-2017-4974 Blind SQL Injection with privileged Cloud Foundry UAA endpoints maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-06-13 medium5.9 CVE-2017-4970 An issue was discovered in Cloud Foundry Foundation cf-release v255 and Staticfile buildpack versions v1.4.0 - v1.4.3. cloudfoundry · cf-release, cloudfoundry · staticfile_buildpack 2017-06-13 medium6.5 CVE-2016-8219 An issue was discovered in Cloud Foundry Foundation cf-release versions prior to 250 and CAPI-release versions prior to 1.12.0. cloudfoundry · capi-release, cloudfoundry · cf-release 2017-06-13 medium6.5 CVE-2016-2165 The Loggregator Traffic Controller endpoints in cf-release v231 and lower, Pivotal Elastic Runtime versions prior to 1.5.19 AND 1.6.x versions prior to 1.6.20 … cloudfoundry · cf-release, pivotal_software · cloud_foundry_elastic_runtime 2017-05-25 medium6.1 CVE-2016-0781 The UAA OAuth approval pages in Cloud Foundry v208 to v231, Login-server v1.6 to v1.14, UAA v2.0.0 to v2.7.4.1, UAA v3.0.0 to v3.2.0, UAA-Release v2 to v7 and … cloudfoundry · cloud_foundry_uaa_bosh, pivotal_software · cloud_foundry, pivotal_software · cloud_foundry_elastic_runtime +2 2017-05-25 medium6.1 CVE-2015-3190 With Cloud Foundry Runtime cf-release versions v209 or earlier, UAA Standalone versions 2.2.6 or earlier and Pivotal Cloud Foundry Runtime 1.4.5 or earlier the… cloudfoundry · cf-release, pivotal_software · cloud_foundry_elastic_runtime, pivotal_software · cloud_foundry_uaa 2017-05-25 medium6.5 CVE-2015-1834 A path traversal vulnerability was identified in the Cloud Foundry component Cloud Controller that affects cf-release versions prior to v208 and Pivotal Cloud … cloudfoundry · cf-release, pivotal_software · cloud_foundry_elastic_runtime 2017-05-25 medium5.9 CVE-2016-5016 Pivotal Cloud Foundry 239 and earlier, UAA (aka User Account and Authentication Server) 3.4.1 and earlier, UAA release 12.2 and earlier, PCF (aka Pivotal Cloud… maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-04-24 medium6.5 CVE-2017-4969 The Cloud Controller in Cloud Foundry cf-release versions prior to v255 allows authenticated developer users to exceed memory and disk quotas for tasks. cloudfoundry · cf-release 2017-04-20 medium5.3 CVE-2016-6636 The OAuth authorization implementation in Pivotal Cloud Foundry (PCF) before 242; UAA 2.x before 2.7.4.7, 3.x before 3.3.0.5, and 3.4.x before 3.4.4; UAA BOSH … cloudfoundry · cloud_foundry_uaa_bosh, pivotal_software · cloud_foundry, pivotal_software · cloud_foundry_elastic_runtime +2 2016-09-30

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.