CVE-2014-0894 json
RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics allows context-dependent attackers t…
published 2014-07-07 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0924
- cvss
- 3.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics allows context-dependent attackers to discover database credentials by reading the DbUser and DbPass fields in an XML document.
Timeline
- First public exploit (EDB-33942)
- Published
Exploit prediction
4.00% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-33942 IBM Algorithmics RICOS 4.5.0 < 4.7.0 - Multiple Vulnerabilities webapps, 2014-07-01
- sec-consult.com https://www.sec-consult.com/fxdata/seccons/prod/temedia/advisories_txt/20140630-0_IBM_Algorithmics_RICOS_multiple_vulnerabilities_v10.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
sec-consult.com
/fxdata/seccons/prod/temedia/advisories_txt/20140630-0_IBM_Algorithmics_RICOS_multiple_vulnerabilities_v10.txt
exploit
-
www-01.ibm.com
/support/docview.wss?uid=swg21675881
vendor-advisory
- packetstormsecurity.com /files/127304/IBM-Algorithmics-RICOS-Disclosure-XSS-CSRF.html
-
securityfocus.com
/archive/1/532598/100/0/threaded
mailing-list
-
secunia.com
/advisories/59296
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/91313
vdb-entry
-
seclists.org
/fulldisclosure/2014/Jun/173
mailing-list
Sources
- CVE List CVE-2014-0894
- NVD CVE-2014-0894
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.