| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Swagger UI up to 3.23.10 and classified as problematic. Affected by this issue is some unknown functionality of the component CSS Handler. The manipulation as part of JSON Data results in injection. This vulnerability is cataloged as CVE-2019-17495. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Swagger UI up to 3.23.10. Affected is an unknown code of the component CSS Handler. The manipulation as part of a JSON Data leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on integrity. CVE summarizes:
A Cascading Style Sheets (CSS) injection vulnerability in Swagger UI before 3.23.11 allows attackers to use the Relative Path Overwrite (RPO) technique to perform CSS-based input field value exfiltration, such as exfiltration of a CSRF token value. In other words, this product intentionally allows the embedding of untrusted JSON data from remote servers, but it was not previously known that <style>@import within the JSON data was a functional attack method.
The weakness was shared 10/10/2019. This vulnerability is traded as CVE-2019-17495 since 10/10/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1055.
Upgrading to version 3.23.11 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0559). Once again VulDB remains the best source for vulnerability data.
Affected
- IBM Rational Build Forge
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: UI 3.23.11
Timeline
10/10/2019 🔍10/10/2019 🔍
10/11/2019 🔍
03/02/2026 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2019-17495 (🔍)
GCVE (CVE): GCVE-0-2019-17495
GCVE (VulDB): GCVE-100-143364
CERT Bund: WID-SEC-2026-0559 - IBM Rational Build Forge: Mehrere Schwachstellen
Entry
Created: 10/11/2019 09:48Updated: 03/02/2026 13:33
Changes: 10/11/2019 09:48 (38), 10/01/2020 14:39 (17), 01/08/2024 07:54 (5), 03/02/2026 13:33 (25)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.