CVE-2014-2845 Vulnerability Analysis & Exploit Details

CVE-2014-2845
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2014-2845 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2014-2845 Details

Status: Modified

Last updated: 🕑 21 Nov 2024, 02:07 UTC
Originally published on: 🕕 15 Nov 2017, 18:29 UTC

Time between publication and last update: 2562 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE-2014-2845 Vulnerability Summary

CVE-2014-2845: Cyberduck before 4.4.4 on Windows does not properly validate X.509 certificate chains, which allows man-in-the-middle attackers to spoof FTP-SSL servers via a certificate issued by an arbitrary root Certification Authority.

Assessing the Risk of CVE-2014-2845

Access Complexity Graph

The exploitability of CVE-2014-2845 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2014-2845

CVE-2014-2845 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2014-2845, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2014-2845, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2014-2845 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2014-2845 poses no threat to data integrity.
  • Availability: None
    CVE-2014-2845 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.066% (probability of exploit)

EPSS Percentile: 32.09% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 67.91% of others.

CVE-2014-2845 References

External References

CWE Common Weakness Enumeration

CWE-295

CAPEC Common Attack Pattern Enumeration and Classification

  • Creating a Rogue Certification Authority Certificate CAPEC-459 An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
  • Signature Spoofing by Improper Validation CAPEC-475 An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key.

Vulnerable Configurations

  • cpe:2.3:a:cyberduck:cyberduck:2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.4:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.5:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.6:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.7:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.8:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:2.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:2.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.0:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.4:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.5:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.6:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.7:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.8:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:3.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:3.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.0:-:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.0:beta:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.0:beta:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.4:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cyberduck:cyberduck:4.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:cyberduck:cyberduck:4.4.3:*:*:*:*:*:*:*
  • cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
    cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2014-2845: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...
  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...