NetSight

Security Dashboard

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

Reset
1,976 matching advisories · page 10 of 66Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2024-54004 Jenkins Filesystem List Parameter Plugin has Path Traversal vulnerability maven · aendter.jenkins.plugins:filesystem-list-parameter-plugin 2024-11-27 high8.0 CVE-2024-54003 Jenkins Simple Queue Plugin has stored cross-site scripting (XSS) vulnerability maven · io.jenkins.plugins:simple-queue 2024-11-27 high8.8 CVE-2024-52554 Script security bypass vulnerability in Jenkins Shared Library Version Override Plugin maven · io.jenkins.plugins:shared-library-version-override 2024-11-13 high8.8 CVE-2024-52553 Session fixation vulnerability in Jenkins OpenId Connect Authentication Plugin maven · org.jenkins-ci.plugins:oic-auth 2024-11-13 high8.0 CVE-2024-52552 Stored XSS vulnerability in Jenkins Authorize Project Plugin maven · org.jenkins-ci.plugins:authorize-project 2024-11-13 high8.0 CVE-2024-52551 Restarting a run with revoked script approval allowed by Jenkins Pipeline: Declarative Plugin maven · org.jenkinsci.plugins:pipeline-model-parent 2024-11-13 high8.0 CVE-2024-52550 Rebuilding a run with revoked script approval allowed by Jenkins Pipeline: Groovy Plugin maven · org.jenkins-ci.plugins.workflow:workflow-cps 2024-11-13 medium4.3 CVE-2024-52549 Missing permission check in Jenkins Script Security Plugin maven · org.jenkins-ci.plugins:script-security 2024-11-13 critical8.1 CVE-2024-47807 Jenkins OpenId Connect Authentication Plugin lacks issuer claim validation maven · org.jenkins-ci.plugins:oic-auth 2024-10-02 critical8.1 CVE-2024-47806 Jenkins OpenId Connect Authentication Plugin lacks audience claim validation maven · org.jenkins-ci.plugins:oic-auth 2024-10-02 high7.5 CVE-2024-47805 Jenkins Credentials plugin reveals encrypted values of credentials to users with Extended Read permission maven · org.jenkins-ci.plugins:credentials 2024-10-02 medium4.3 CVE-2024-47804 Jenkins item creation restriction bypass vulnerability maven · org.jenkins-ci.main:jenkins-core 2024-10-02 medium4.3 CVE-2024-47803 Jenkins exposes multi-line secrets through error messages maven · org.jenkins-ci.main:jenkins-core 2024-10-02 medium5.4 CVE-2024-43045 Jenkins does not perform a permission check in an HTTP endpoint maven · org.jenkins-ci.main:jenkins-core 2024-08-07 high9.0 CVE-2024-43044 Jenkins Remoting library arbitrary file read vulnerability maven · org.jenkins-ci.main:remoting, maven · org.jenkins-ci.main:jenkins-core 2024-08-07 medium4.3 CVE-2024-39460 Bitbucket OAuth access token exposed in the build log by Bitbucket Branch Source Plugin maven · org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source 2024-06-26 medium4.3 CVE-2024-39459 Secret file credentials stored unencrypted in rare cases by Plain Credentials Plugin maven · org.jenkins-ci.plugins:plain-credentials 2024-06-26 low3.1 CVE-2024-39458 Exposure of secrets through system log in Jenkins Structs Plugin maven · org.jenkins-ci.plugins:structs 2024-06-26 medium4.3 CVE-2024-5273 Jenkins Report Info Plugin Path Traversal vulnerability maven · org.jenkins-ci.plugins:report-info 2024-05-24 medium6.8 CVE-2024-34148 Jenkins Subversion Partial Release Manager Plugin programmatically disables the fix for CVE-2016-3721 maven · org.jenkins-ci.plugins:partial-release-manager 2024-05-02 medium4.3 CVE-2024-34147 Jenkins Telegram Bot Plugin stores the Telegram Bot token in plaintext maven · org.jenkins-ci.plugins:telegrambot 2024-05-02 medium5.3 CVE-2024-34146 Jenkins Git server Plugin does not perform a permission check maven · org.jenkins-ci.plugins:git-server 2024-05-02 high8.8 CVE-2024-34145 Jenkins Script Security Plugin sandbox bypass vulnerability maven · org.jenkins-ci.plugins:script-security 2024-05-02 critical9.8 CVE-2024-34144 Jenkins Script Security Plugin has sandbox bypass vulnerability involving crafted constructor bodies maven · org.jenkins-ci.plugins:script-security 2024-05-02 medium4.3 CVE-2024-3825 BlazeMeter Jenkins plugin vulnerable to Cross-Site Request Forgery maven · com.blazemeter.plugins:BlazeMeterJenkinsPlugin 2024-04-17 high8.8 CVE-2024-2216 Jenkins docker-build-step Plugin missing permission check maven · org.jenkins-ci.plugins:docker-build-step 2024-03-06 medium6.3 CVE-2024-2215 Jenkins docker-build-step Plugin Cross-Site Request Forgery vulnerability maven · org.jenkins-ci.plugins:docker-build-step 2024-03-06 medium4.2 CVE-2024-28162 Jenkins Delphix Plugin has improper SSL/TLS certificate validation maven · org.jenkins-ci.plugins:delphix 2024-03-06 medium4.8 CVE-2024-28161 Jenkins Delphix Plugin has SSL/TLS certificate validation disabled by default maven · org.jenkins-ci.plugins:delphix 2024-03-06 high8.8 CVE-2024-28160 Jenkins iceScrum Plugin vulnerable to stored Cross-site Scripting maven · org.jenkins-ci.plugins:icescrum 2024-03-06

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.