Sonar CVEs
9 CVEs
Overview 9 matches · 0 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
1
11.1%
No exploit published
8
88.9%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
9
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
11.1%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
8
88.9%
split by
peak 2 / year
20131
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
20140
20150
20160
20170
20181
No exploit published1
Medium1
not blocked1
No public exploit1
20192
No exploit published2
High1
Medium1
not blocked2
No public exploit2
20202
No exploit published2
Medium2
not blocked2
No public exploit2
20210
20221
No exploit published1
Medium1
not blocked1
No public exploit1
20231
No exploit published1
Medium1
not blocked1
No public exploit1
20241
No exploit published1
Medium1
not blocked1
No public exploit1
201320142015201620172018201920202021202220232024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-38460 | Medium | 2024-06-16 | No exploit published | No public exploit | In SonarQube before 10.4 and 9.9.4 LTA, encrypted values generated using the Settings Encryption feature are potentially exposed in cleartext as part of the URL parameters in the logs (such as SonarQube Access Logs, Proxy Logs, etc). |
| CVE-2023-35145 | Medium | 2023-06-14 | No exploit published | No public exploit | Jenkins Sonargraph Integration Plugin 5.0.1 and earlier does not escape the file path and the project name for the Log file field form validation, resulting in a stored cross-site scripting vulnerability exploitable by attackers with Item/Configure permission. |
| CVE-2022-46688 | Medium | 2022-12-12 | No exploit published | No public exploit | A cross-site request forgery (CSRF) vulnerability in Jenkins Sonar Gerrit Plugin 377.v8f3808963dc5 and earlier allows attackers to have Jenkins connect to Gerrit servers (previously configured by Jenkins administrators) using attacker-specified credentials IDs obtained through another method, potentially capturing credentials stored in Jenkins. |
| CVE-2020-2201 | Medium | 2020-07-02 | No exploit published | No public exploit | Jenkins Sonargraph Integration Plugin 3.0.0 and earlier does not escape the file path for the Log file field form validation, resulting in a stored cross-site scripting vulnerability. |
| CVE-2020-2150 | Medium | 2020-03-09 | No exploit published | No public exploit | Jenkins Sonar Quality Gates Plugin 1.3.1 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, potentially resulting in their exposure. |
| CVE-2019-10467 | Medium | 2019-10-23 | No exploit published | No public exploit | Jenkins Sonar Gerrit Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system. |
| CVE-2018-1000425 | High | 2019-01-09 | No exploit published | No public exploit | An insufficiently protected credentials vulnerability exists in Jenkins SonarQube Scanner Plugin 2.8 and earlier in SonarInstallation.java that allows attackers with local file system access to obtain the credentials used to connect to SonarQube. |
| CVE-2018-19413 | Medium | 2018-12-14 | No exploit published | No public exploit | A vulnerability in the API of SonarSource SonarQube before 7.4 could allow an authenticated user to discover sensitive information such as valid user-account logins in the web application. The vulnerability occurs because of improperly configured access controls that cause the API to return the externalIdentity field to non-administrator users. The attacker could use this information in subsequent attacks against the system. |
| CVE-2013-5676 | Medium | 2013-12-13 | Mitigation candidate | Working exploit published | The Jenkins Plugin for SonarQube 3.7 and earlier allows remote authenticated users to obtain sensitive information (cleartext passwords) by reading the value in the sonar.sonarPassword parameter from jenkins/configure. |