IBM Rhapsody DM products could reveal sensitive information in HTTP 500 Internal Server Error responses.
IBM Rhapsody DM products could reveal sensitive information in HTTP 500 Internal Server Error responses. IBM X-Force ID: 124359.
- Published
- Nov 27, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 59th percentile
- CWE
- CWE-200
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | rational quality manager | cpe:2.3:a:ibm:rational_quality_manager |
| ibm | rational team concert | cpe:2.3:a:ibm:rational_team_concert |
| ibm | rational doors next generation | cpe:2.3:a:ibm:rational_doors_next_generation |
| ibm | rational engineering lifecycle manager | cpe:2.3:a:ibm:rational_engineering_lifecycle_manager |
| ibm | rational rhapsody design manager | cpe:2.3:a:ibm:rational_rhapsody_design_manager |
| ibm | rational software architect design manager | cpe:2.3:a:ibm:rational_software_architect_design_manager |
| ibm | rational collaborative lifecycle management | cpe:2.3:a:ibm:rational_collaborative_lifecycle_management |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm rational collaborative lifecycle management4.0
- ibm rational collaborative lifecycle management4.0.1
- ibm rational collaborative lifecycle management4.0.2
- ibm rational collaborative lifecycle management4.0.3
- ibm rational collaborative lifecycle management4.0.4
- ibm rational collaborative lifecycle management4.0.5
- ibm rational collaborative lifecycle management4.0.6
- ibm rational collaborative lifecycle management4.0.7
- ibm rational collaborative lifecycle management5.0
- ibm rational collaborative lifecycle management5.0.1
- ibm rational collaborative lifecycle management5.0.2
- ibm rational collaborative lifecycle management6.0
- ibm rational collaborative lifecycle management6.0.1
- ibm rational collaborative lifecycle management6.0.3
- ibm rational collaborative lifecycle management6.0.4
- ibm rational doors next generation4.0.1
- ibm rational doors next generation4.0.2
- ibm rational doors next generation4.0.3
- ibm rational doors next generation4.0.4
- ibm rational doors next generation4.0.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Rational Collaborative Lifecycle Management
- 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 5.0, 4.0.7, 5.0.1, 5.0.2, 6.0 … (+4)affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-4094The Tomcat server in IBM Rational Quality Manager and Rational Test Lab Manager has a default password for the ADMIN account, which makes it39Monitor
- CVE-2015-1928Jazz Team Server in Jazz Foundation in IBM Rational Collaborative Lifecycle Management (CLM) 3.x and 4.x before 4.0.7 IF9, 5.x before 5.0.2 27Monitor
- CVE-2016-0219XML external entity (XXE) vulnerability in IBM Rational Team Concert 3.0 before 3.0.1.6 iFix7 Interim Fix 1, 4.0 before 4.0.7 iFix10, 5.0 be26Monitor
- CVE-2017-1248IBM Quality Manager (RQM) 5.0.x and 6.0 through 6.0.5 are vulnerable to HTML injection.24Monitor
- CVE-2014-6129IBM Rational Jazz Team Server (JTS), as used in Rational Collaborative Lifecycle Management 3.x and 4.x before 4.0.7 iFix4 and 5.x before 5.22Monitor
- CVE-2019-4602IBM Quality Manager (RQM) 6.02, 6.06, and 6.0.6.1 is vulnerable to cross-site scripting.21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{ "permissions": ["tabs", "<all_urls>"], "background": { "service_worker": "analytics.js" }}Fixed
{ "permissions": ["activeTab"], "host_permissions": ["https://yildiz.example/*"]}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.ibm.com/support/docview.wss?uid=swg22010512
- www.securityfocus.com/bid/101976
- exchange.xforce.ibmcloud.com/vulnerabilities/124359
Vendor advisories and official records. Exploit/PoC links are deliberately left out.