Apache CXF Fediz up to 1.2.3/1.3.1 Plugins cross-site request forgery

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Apache CXF Fediz up to 1.2.3/1.3.1. This impacts an unknown function of the component Plugins. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2017-7661. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Apache CXF Fediz up to 1.2.3/1.3.1 (Application Server Software). It has been rated as problematic. This issue affects some unknown processing of the component Plugins. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
Apache CXF Fediz ships with a number of container-specific plugins to enable WS-Federation for applications. A CSRF (Cross Style Request Forgery) style vulnerability has been found in the Spring 2, Spring 3, Jetty 8 and Jetty 9 plugins in Apache CXF Fediz prior to 1.4.0, 1.3.2 and 1.2.4.
The bug was discovered 05/16/2017. The weakness was shared 05/16/2017 (Website). The advisory is shared at cxf.apache.org. The identification of this vulnerability is CVE-2017-7661 since 04/11/2017. 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.
Upgrading to version 1.2.4, 1.3.2 or 1.4.0 eliminates this vulnerability.
The entry VDB-101430 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: CXF Fediz 1.2.4/1.3.2/1.4.0
Timeline
04/11/2017 🔍05/16/2017 🔍
05/16/2017 🔍
05/16/2017 🔍
05/17/2017 🔍
12/24/2020 🔍
Sources
Vendor: apache.orgAdvisory: cxf.apache.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-7661 (🔍)
GCVE (CVE): GCVE-0-2017-7661
GCVE (VulDB): GCVE-100-101429
OSVDB: - CVE-2017-7661 - Apache - CXF - Cross-Site Request Forgery Issue
SecurityTracker: 1038497
See also: 🔍
Entry
Created: 05/17/2017 08:04Updated: 12/24/2020 15:42
Changes: 05/17/2017 08:04 (59), 09/29/2020 13:01 (3), 12/24/2020 15:42 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.