The ODE process deployment web service was sensible to deployment messages with forged names. Using a path for the name was allowing directory traversal, resulting in the potential writing of files under unwanted locations, the overwriting of existing files or their deletion. This issue was addressed in Apache ODE 1.3.3 which was released in 2009, however the incorrect name CVE-2008-2370 was used on the advisory by mistake.
Vector
NETWORK
Complexity
LOW
Authentication
NONE
Confidentiality
NONE
Integrity
PARTIAL
Availability
PARTIAL
Apache Ode 1.0 Incubating (not an official CPE)
Apache Ode 1.0 Rc1-incubating (not an official CPE)
Apache Ode 1.0 Rc2-incubating (not an official CPE)
Apache Ode 1.0 Rc3-incubating (not an official CPE)
Apache Ode 1.0 Rc4-incubating (not an official CPE)
Apache Ode 1.1 Rc1 (not an official CPE)
Apache Ode 1.1 Rc2 (not an official CPE)
Apache Ode 1.1 Rc3 (not an official CPE)
Apache Ode 1.1 Rc4 (not an official CPE)
Apache Ode 1.1 Rc5 (not an official CPE)
Apache Ode 1.1.1 Rc1 (not an official CPE)
Advisory | Patch | Confirmed | Link |
---|---|---|---|
[user] 20180304 CVE-2018-1316 used to cover issue incorr... | |||
[www-announce] 20090808 Apache ODE 1.3.3 |
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (ID 22)
Related CAPEC 7
Relative Path Traversal (CAPEC-ID 139)
Directory Traversal (CAPEC-ID 213)
File System Function Injection, Content Based (CAPEC-ID 23)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (CAPEC-ID 64)
Manipulating Input to File System Calls (CAPEC-ID 76)
Using Escaped Slashes in Alternate Encoding (CAPEC-ID 78)
Using Slashes in Alternate Encoding (CAPEC-ID 79)