What is the CVSS score of CVE-2014-0865?

CVE-2014-0865 has a CVSS 2.0 base score of 4.9 (Medium). CVSS vector: AV:N/AC:M/Au:S/C:N/I:P/A:P. EPSS exploitation probability: 8.5%.

Is there a public PoC exploit available for CVE-2014-0865?

Yes, a public proof-of-concept exploit is available for CVE-2014-0865. Prioritise patching immediately. EPSS: 8.5%.

Algo Credit Limits CVE-2014-0865

MEDIUM

Improper Input Validation (CWE-20)

2014-07-07 psirt@us.ibm.com

IBM Authentication Bypass Algo Credit Limits Algorithmics

4.9

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.9 MEDIUM

AV:N/AC:M/Au:S/C:N/I:P/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:N/I:P/A:P

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

Lifecycle Timeline

CVE Published

Jul 07, 2014 - 11:01 cve.org

MEDIUM 4.9

DescriptionCVE.org

RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics relies on client-side input validation, which allows remote authenticated users to bypass intended dual-control restrictions and modify data via crafted serialized objects, as demonstrated by limit manipulations.

AnalysisAI

RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics relies on client-side input validation, which allows remote authenticated users to bypass. Rated medium severity (CVSS 4.9), this vulnerability is remotely exploitable. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-20. RICOS in IBM Algo Credit Limits (aka ACLM) 4.5.0 through 4.7.0 before 4.7.0.03 FP5 in IBM Algorithmics relies on client-side input validation, which allows remote authenticated users to bypass intended dual-control restrictions and modify data via crafted serialized objects, as demonstrated by limit manipulations. Affected products include: Ibm Algo Credit Limits, Ibm Algorithmics. Version information: through 4.7.0.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.