NetSight

Security Dashboard

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

Reset
1,976 matching advisories · page 14 of 66Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2023-40349 Jenkins Gogs Plugin vulnerable to unsafe default behavior and information disclosure maven · org.jenkins-ci.plugins:gogs-webhook 2023-08-16 medium6.5 CVE-2023-40348 Jenkins Gogs Plugin vulnerable to unsafe default behavior and information disclosure maven · org.jenkins-ci.plugins:gogs-webhook 2023-08-16 medium4.3 CVE-2023-40347 Jenkins Maven Artifact ChoiceListProvider (Nexus) Plugin vulnerable to exposure of system-scoped credentials maven · org.jenkins-ci.plugins:maven-artifact-choicelistprovider 2023-08-16 high8.0 CVE-2023-40346 Jenkins Shortcut Job Plugin stored cross-site scripting vulnerability maven · io.jenkins.plugins:shortcut-job 2023-08-16 medium4.3 CVE-2023-40345 Jenkins Delphix Plugin vulnerable to exposure of system-scoped credentials maven · org.jenkins-ci.plugins:delphix 2023-08-16 medium4.3 CVE-2023-40344 Jenkins Delphix Plugin missing permission check maven · org.jenkins-ci.plugins:delphix 2023-08-16 medium5.9 CVE-2023-40343 Jenkins Tuleap Authentication Plugin non-constant time token comparison maven · io.jenkins.plugins:tuleap-oauth 2023-08-16 high8.0 CVE-2023-40342 Jenkins Flaky Test Handler Plugin stored cross-site scripting vulnerability maven · org.jenkins-ci.plugins:flaky-test-handler 2023-08-16 high8.8 CVE-2023-40341 Jenkins Blue Ocean Plugin cross-site request forgery vulnerability maven · io.jenkins.blueocean:blueocean 2023-08-16 high7.5 CVE-2023-40340 Jenkins NodeJS Plugin 1.6.0 and earlier does not properly mask (i.e., replace with asterisks) credentials specified in the Npm config file in Pipeline build lo… maven · org.jenkins-ci.plugins:nodejs 2023-08-16 high7.5 CVE-2023-40339 Jenkins Config File Provider Plugin improper credential masking vulnerability maven · org.jenkins-ci.plugins:config-file-provider 2023-08-16 medium4.3 CVE-2023-40338 Jenkins Folders Plugin information disclosure vulnerability maven · org.jenkins-ci.plugins:cloudbees-folder 2023-08-16 medium4.3 CVE-2023-40337 Jenkins Folders Plugin cross-site request forgery vulnerability maven · org.jenkins-ci.plugins:cloudbees-folder 2023-08-16 high8.0 CVE-2023-40336 Jenkins Folders Plugin cross-site request forgery vulnerability maven · org.jenkins-ci.plugins:cloudbees-folder 2023-08-16 high7.7 CVE-2023-3442 Missing authorization in Jenkins Plug-in for ServiceNow maven · io.jenkins.plugins:servicenow-devops 2023-07-26 medium6.1 CVE-2023-3414 Credential leakage in Jenkins Plug-in for ServiceNow maven · io.jenkins.plugins:servicenow-devops 2023-07-26 medium4.3 CVE-2023-39156 CSRF vulnerability in Bazaar Plugin maven · org.jenkins-ci.plugins:bazaar 2023-07-26 medium5.3 CVE-2023-39155 Secret displayed without masking by Chef Identity Plugin maven · org.jenkins-ci.plugins:chef-identity 2023-07-26 medium4.2 CVE-2023-39154 Incorrect permission checks in Qualys Web App Scanning Connector Plugin allow capturing credentials maven · com.qualys.plugins:qualys-was 2023-07-26 medium5.4 CVE-2023-39153 CSRF vulnerability in GitLab Authentication Plugin maven · org.jenkins-ci.plugins:gitlab-oauth 2023-07-26 medium6.5 CVE-2023-39152 Incorrect control flow in Jenkins Gradle Plugin breaks credentials masking in the build log maven · org.jenkins-ci.plugins:gradle 2023-07-26 high8.0 CVE-2023-39151 Jenkins Stored Cross-site Scripting vulnerability maven · org.jenkins-ci.main:jenkins-core 2023-07-26 low2.6 CVE-2023-32263 Potential leak of credentials in Micro Focus Dimensions CM Jenkins Plugin maven · org.jenkins-ci.plugins:dimensionsscm 2023-07-19 medium4.3 CVE-2023-32262 Exposure of system-scoped credentials in Jenkins Dimensions Plugin maven · org.jenkins-ci.plugins:dimensionsscm 2023-07-19 medium4.2 CVE-2023-32261 Missing permission check in Jenkins Dimensions Plugin allows enumerating credentials IDs maven · org.jenkins-ci.plugins:dimensionsscm 2023-07-19 high7.1 CVE-2023-37965 A missing permission check in Jenkins ElasticBox CI Plugin 5.0.1 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified … maven · org.jenkins-ci.plugins:elasticbox 2023-07-12 high8.8 CVE-2023-37964 A cross-site request forgery (CSRF) vulnerability in Jenkins ElasticBox CI Plugin 5.0.1 and earlier allows attackers to connect to an attacker-specified URL us… maven · org.jenkins-ci.plugins:elasticbox 2023-07-12 medium5.4 CVE-2023-37963 Jenkins Benchmark Evaluator Plugin missing permission check maven · io.jenkins.plugins:benchmark-evaluator 2023-07-12 high8.8 CVE-2023-37962 Jenkins Benchmark Evaluator Plugin vulnerable to cross-site request forgery maven · io.jenkins.plugins:benchmark-evaluator 2023-07-12 high8.8 CVE-2023-37961 Jenkins Assembla Auth Plugin vulnerable to cross-site request forgery maven · org.jenkins-ci.plugins:assembla-auth 2023-07-12

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.