NetSight

Security Dashboard

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

Reset
129 matching advisories · page 3 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2019-3782 Cloud Foundry CredHub CLI, versions prior to 2.2.1, inadvertently writes authentication credentials provided via environment variables to its persistent config… cloudfoundry · credhub_cli 2019-02-13 critical9.9 CVE-2018-15761 Cloud Foundry UAA Privilege Escalation maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2018-11-19 medium6.6 CVE-2018-11082 Cloud Foundry UAA, all versions prior to 4.20.0 and Cloud Foundry UAA Release, all versions prior to 61.0, allows brute forcing of MFA codes. pivotal_software · cloudfoundry_uaa, pivotal_software · cloudfoundry_uaa_release 2018-10-05 medium6.8 CVE-2018-11084 Cloud Foundry Garden-runC release, versions prior to 1.16.1, prevents deletion of some app environments based on file attributes. cloudfoundry · garden-runc 2018-09-18 high7.5 CVE-2018-11047 Cloud Foundry UAA accepts refresh token as access token on admin endpoints maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2018-07-24 medium5.9 CVE-2016-0708 Applications deployed to Cloud Foundry, versions v166 through v227, may be vulnerable to a remote disclosure of information, including, but not limited to envi… cloudfoundry · cf-release, cloudfoundry · java_buildpack 2018-07-11 medium6.1 CVE-2018-11041 Cloud Foundry UAA open redirect maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2018-06-25 medium6.5 CVE-2018-1269 Cloud Foundry Loggregator, versions 89.x prior to 89.5 or 96.x prior to 96.1 or 99.x prior to 99.1 or 101.x prior to 101.9 or 102.x prior to 102.2, does not ha… cloudfoundry · loggregator 2018-06-06 medium6.8 CVE-2018-1268 Cloud Foundry Loggregator, versions 89.x prior to 89.5 or 96.x prior to 96.1 or 99.x prior to 99.1 or 101.x prior to 101.9 or 102.x prior to 102.2, does not va… cloudfoundry · loggregator 2018-06-06 high7.2 CVE-2018-1265 Cloud Foundry Diego, release versions prior to 2.8.0, does not properly sanitize file paths in tar and zip files headers. cloudfoundry · cf-deployment, pivotal_software · cloud_foundry_diego 2018-06-06 medium5.3 CVE-2018-1193 Cloud Foundry routing-release, versions prior to 0.175.0, lacks sanitization for user-provided X-Forwarded-Proto headers. cloudfoundry · cf-deployment, cloudfoundry · routing-release 2018-05-23 high7.2 CVE-2018-1262 UAA privilege escalation across identity zones maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2018-05-15 medium6.5 CVE-2018-1277 Cloud Foundry Garden-runC, versions prior to 1.13.0, does not correctly enforce disc quotas for Docker image layers. cloudfoundry · garden-runc, cloudfoundry · cf-deployment 2018-04-30 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 critical9.6 CVE-2016-6658 Applications in cf-release before 245 can be configured and pushed with a user-provided custom buildpack using a URL pointing to the buildpack. cloudfoundry · cf-release, pivotal_software · cloud_foundry_elastic_runtime 2018-03-29 high8.8 CVE-2018-1191 Cloud Foundry Garden-runC, versions prior to 1.11.0, contains an information exposure vulnerability. cloudfoundry · cf-deployment, cloudfoundry · garden-runc-release 2018-03-29 high8.1 CVE-2018-1267 Cloud Foundry Silk CNI plugin, versions prior to 0.2.0, contains an improper access control vulnerability. cloudfoundry · silk-release 2018-03-27 high8.1 CVE-2018-1266 Cloud Foundry Cloud Controller, versions prior to 1.52.0, contains information disclosure and path traversal vulnerabilities. cloudfoundry · capi-release 2018-03-27 high8.1 CVE-2018-1221 In cf-deployment before 1.14.0 and routing-release before 0.172.0, the Cloud Foundry Gorouter mishandles WebSocket requests for AWS Application Load Balancers … cloudfoundry · cf-deployment, cloudfoundry · routing-release 2018-03-19 high8.8 CVE-2018-1195 In Cloud Controller versions prior to 1.46.0, cf-deployment versions prior to 1.3.0, and cf-release versions prior to 283, Cloud Controller accepts refresh tok… cloudfoundry · capi-release, cloudfoundry · cf-deployment, cloudfoundry · cf-release 2018-03-19 high7.5 CVE-2015-5350 In Garden versions 0.22.0-0.329.0, a vulnerability has been discovered in the garden-linux nstar executable that allows access to files on the host system. cloudfoundry · garden 2018-03-19 high8.8 CVE-2018-1192 Cloud Foundry UAA SessionID present in Audit Event Logs maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2018-02-01 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 high8.8 CVE-2015-5173 Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow attackers to have unspecified… cloudfoundry · cf-release, pivotal_software · cloud_foundry_elastic_runtime, pivotal_software · cloud_foundry_uaa 2017-10-24 critical9.8 CVE-2015-5172 Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow attackers to have unspecified… maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-10-24 critical9.8 CVE-2015-5171 The password change functionality in Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.… maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-10-24 high8.8 CVE-2015-5170 Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow remote attackers to conduct c… maven · org.cloudfoundry.identity:cloudfoundry-identity-server 2017-10-24 high7.8 CVE-2017-8048 In Cloud Foundry capi-release versions 1.33.0 and later, prior to 1.42.0 and cf-release versions 268 and later, prior to 274, the original fix for CVE-2017-803… cloudfoundry · cf-release, pivotal · capi-release 2017-10-04

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.