| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Apache jUDDI 3.1./3.1.2/3.1.3/3.1.4. Impacted is an unknown function of the component Logout. The manipulation leads to redirect. This vulnerability is listed as CVE-2015-5241. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Apache jUDDI 3.1./3.1.2/3.1.3/3.1.4. This issue affects some unknown processing of the component Logout. The manipulation with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
After logging into the portal, the logout jsp page redirects the browser back to the login page after. It is feasible for malicious users to redirect the browser to an unintended web page in Apache jUDDI 3.1.2, 3.1.3, 3.1.4, and 3.1.5 when utilizing the portlets based user interface also known as 'Pluto', 'jUDDI Portal', 'UDDI Portal' or 'uddi-console'. User session data, credentials, and auth tokens are cleared before the redirect.
The bug was discovered 07/01/2015. The weakness was presented 05/19/2017 (Website). The advisory is shared at juddi.apache.org. The identification of this vulnerability is CVE-2015-5241 since 07/01/2015. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/30/2020). MITRE ATT&CK project uses the attack technique T1204.001 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 688 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-113106 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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: RedirectCWE: CWE-601
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/01/2015 🔍07/01/2015 🔍
05/19/2017 🔍
05/19/2017 🔍
05/20/2017 🔍
09/30/2020 🔍
Sources
Vendor: apache.orgAdvisory: juddi.apache.org
Status: Not defined
CVE: CVE-2015-5241 (🔍)
GCVE (CVE): GCVE-0-2015-5241
GCVE (VulDB): GCVE-100-101513
OSVDB: - CVE-2015-5241 - Apache - jUDDI - Open Redirect Issue
See also: 🔍
Entry
Created: 05/20/2017 20:55Updated: 09/30/2020 14:48
Changes: 05/20/2017 20:55 (58), 09/30/2020 14:48 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

No comments yet. Languages: en.
Please log in to comment.