| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Foswiki 1.0.0/1.0.1/1.0.2/1.0.3/1.0.4. It has been classified as problematic. This issue affects some unknown processing. Performing a manipulation results in cross-site request forgery. This vulnerability is reported as CVE-2009-1434. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in Foswiki 1.0.0/1.0.1/1.0.2/1.0.3/1.0.4 (Content Management System). This affects an unknown code block. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Cross-site request forgery (CSRF) vulnerability in Foswiki before 1.0.5 allows remote attackers to hijack the authentication of arbitrary users for requests that modify pages, change permissions, or change group memberships, as demonstrated by a URL for a (1) save or (2) view script in the SRC attribute of an IMG element, a related issue to CVE-2009-1339.
The weakness was disclosed 04/29/2009 (Website). The advisory is shared at sourceforge.net. This vulnerability is uniquely identified as CVE-2009-1434 since 04/27/2009. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
It is declared as highly functional.
Upgrading to version 1.0.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (50256), OSVDB (54148†) and Secunia (SA34863†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Highly functional
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 800613
OpenVAS Name: Foswiki Cross-Site Request Forgery Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Foswiki 1.0.1
Timeline
04/27/2009 🔍04/29/2009 🔍
04/30/2009 🔍
04/30/2009 🔍
04/30/2009 🔍
03/17/2015 🔍
11/07/2018 🔍
Sources
Advisory: sourceforge.netStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2009-1434 (🔍)
GCVE (CVE): GCVE-0-2009-1434
GCVE (VulDB): GCVE-100-47997
X-Force: 50256 - Foswiki unspecified cross-site request forgery
Secunia: 34863 - Foswiki Cross-Site Request Forgery Vulnerabilities, Less Critical
OSVDB: 54148 - Foswiki GET Request Handling Multiple CSRF
Entry
Created: 03/17/2015 23:38Updated: 11/07/2018 16:39
Changes: 03/17/2015 23:38 (57), 11/07/2018 16:39 (5)
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.