NetSight

Security Dashboard

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

Reset
129 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2020-5417 Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also the system domain (which is true in the … cloudfoundry · capi-release, cloudfoundry · cf-deployment 2020-08-21 medium6.5 CVE-2020-5416 Cloud Foundry Routing (Gorouter), versions prior to 0.204.0, when used in a deployment with NGINX reverse proxies in front of the Gorouters, is potentially vul… cloudfoundry · cf-deployment, cloudfoundry · routing-release 2020-08-21 medium5.9 CVE-2020-15586 Go before 1.13.13 and 1.14.x before 1.14.5 has a data race in some net/http servers, as demonstrated by the httputil.ReverseProxy Handler, because it reads a r… golang · go, cloudfoundry · cf-deployment, cloudfoundry · routing-release +3 2020-07-17 high8.8 CVE-2020-5402 In Cloud Foundry UAA, versions prior to 74.14.0, a CSRF vulnerability exists due to the OAuth2 state parameter not being checked in the callback function when … cloudfoundry · cf-deployment, cloudfoundry · user_account_and_authentication 2020-02-27 medium5.3 CVE-2020-5401 Cloud Foundry Routing Release, versions prior to 0.197.0, contains GoRouter, which allows malicious clients to send invalid headers, causing caching layers to … cloudfoundry · routing_release 2020-02-27 medium6.5 CVE-2020-5400 Cloud Foundry Cloud Controller (CAPI), versions prior to 1.91.0, logs properties of background jobs when they are run, which may include sensitive information … cloudfoundry · capi-release, cloudfoundry · cf-deployment 2020-02-27 high7.4 CVE-2020-5399 Cloud Foundry CredHub, versions prior to 2.5.10, connects to a MySQL database without TLS even when configured to use TLS. cloudfoundry · credhub, pivotal_software · cloud_foundry_cf-deployment 2020-02-12 medium4.3 CVE-2019-11294 Cloud Foundry Cloud Controller API (CAPI), version 1.88.0, allows space developers to list all global service brokers, including service broker URLs and GUIDs,… cloudfoundry · capi-release, cloudfoundry · cf-deployment 2019-12-19 medium6.5 CVE-2019-11293 Cloud Foundry UAA Release, versions prior to v74.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter. cloudfoundry · cf-deployment, cloudfoundry · user_account_and_authentication 2019-12-06 high7.5 CVE-2019-11290 Cloud Foundry UAA Release, versions prior to v74.8.0, logs all query parameters to tomcat’s access file. cloudfoundry · cf-deployment, cloudfoundry · user_account_and_authentication 2019-11-26 high7.5 CVE-2019-11289 Cloud Foundry Routing Improper Input Validation vulnerability go · code.cloudfoundry.org/gorouter 2019-11-19 high8.8 CVE-2019-11283 Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs. cloudfoundry · cf-deployment, pivotal_software · cloud_foundry_smb_volume 2019-10-23 medium4.3 CVE-2019-11282 Cloud Foundry UAA, versions prior to v74.3.0, contains an endpoint that is vulnerable to SCIM injection attack. cloudfoundry · cf-deployment, pivotal_software · cloud_foundry_uaa 2019-10-23 high8.8 CVE-2019-11279 CF UAA versions prior to 74.1.0 can request scopes for a client that shouldn't be allowed by submitting an array of requested scopes. cloudfoundry · uaa_release 2019-09-26 high8.8 CVE-2019-11278 CF UAA versions prior to 74.1.0, allow external input to be directly queried against. cloudfoundry · user_account_and_authentication 2019-09-26 high8.1 CVE-2019-11277 Cloud Foundry NFS Volume Service, 1.7.x versions prior to 1.7.11 and 2.x versions prior to 2.3.0, is vulnerable to LDAP injection. cloudfoundry · cf-deployment, cloudfoundry · nfs_volume_release 2019-09-23 medium6.1 CVE-2019-11274 Cloud Foundry UAA, versions prior to 74.0.0, is vulnerable to an XSS attack. cloudfoundry · user_account_and_authentication 2019-08-09 critical9.8 CVE-2019-3801 Cloud Foundry cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fetch dependencies when building. cloudfoundry · cf-deployment, cloudfoundry · credhub, cloudfoundry · uaa_release 2019-04-25 high8.7 CVE-2019-3788 Cloud Foundry UAA Release, versions prior to 71.0, allows clients to be configured with an insecure redirect uri. cloudfoundry · uaa_release 2019-04-25 medium6.5 CVE-2019-3789 Cloud Foundry Routing Release, all versions prior to 0.188.0, contains a vulnerability that can hijack the traffic to route services hosted outside the platfor… cloudfoundry · routing_release 2019-04-24 high7.1 CVE-2019-3786 Cloud Foundry BOSH Backup and Restore CLI, all versions prior to 1.5.0, does not check the authenticity of backup scripts in BOSH. cloudfoundry · bosh_backup_and_restore 2019-04-24 medium6.0 CVE-2019-3798 Cloud Foundry Cloud Controller API Release, versions prior to 1.79.0, contains improper authentication when validating user permissions. cloudfoundry · capi-release 2019-04-17 high8.1 CVE-2019-3785 Cloud Foundry Cloud Controller, versions prior to 1.78.0, contain an endpoint with improper authorization. cloudfoundry · capi-release 2019-03-13 high8.8 CVE-2019-3780 Cloud Foundry Container Runtime, versions prior to 0.28.0, deploys K8s worker nodes that contains a configuration file with IAAS credentials. cloudfoundry · container_runtime 2019-03-08 high8.8 CVE-2019-3779 Cloud Foundry Container Runtime, versions prior to 0.29.0, deploys Kubernetes clusters utilize the same CA (Certificate Authority) to sign and trust certs for … cloudfoundry · container_runtime 2019-03-08 high8.2 CVE-2019-3784 Cloud Foundry Stratos, versions prior to 2.3.0, contains an insecure session that can be spoofed. cloudfoundry · stratos 2019-03-07 high8.8 CVE-2019-3783 Cloud Foundry Stratos, versions prior to 2.3.0, deploys with a public default session store secret. cloudfoundry · stratos 2019-03-07 high8.8 CVE-2019-3781 Cloud Foundry CLI, versions prior to v6.43.0, improperly exposes passwords when verbose/trace/debugging is turned on. cloudfoundry · command_line_interface 2019-03-07 high7.1 CVE-2019-3775 Cloud Foundry UAA, versions prior to v70.0, allows a user to update their own email address. cloudfoundry · uaa_release 2019-03-07 high8.8 CVE-2019-1003025 A exposure of sensitive information vulnerability exists in Jenkins Cloud Foundry Plugin 2.3.1 and earlier in AbstractCloudFoundryPushDescriptor.java that allo… maven · org.jenkins-ci.plugins:cloudfoundry 2019-02-20

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.