ID CVE-2009-0051
Summary ZXID 0.29 and earlier does not properly check the return value from the OpenSSL DSA_verify function, which allows remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature, a similar vulnerability to CVE-2008-5077.
References
Vulnerable Configurations
  • cpe:2.3:a:zxid:zxid:0.1
    cpe:2.3:a:zxid:zxid:0.1
  • cpe:2.3:a:zxid:zxid:0.2
    cpe:2.3:a:zxid:zxid:0.2
  • cpe:2.3:a:zxid:zxid:0.3
    cpe:2.3:a:zxid:zxid:0.3
  • cpe:2.3:a:zxid:zxid:0.4
    cpe:2.3:a:zxid:zxid:0.4
  • cpe:2.3:a:zxid:zxid:0.5
    cpe:2.3:a:zxid:zxid:0.5
  • cpe:2.3:a:zxid:zxid:0.6
    cpe:2.3:a:zxid:zxid:0.6
  • cpe:2.3:a:zxid:zxid:0.7
    cpe:2.3:a:zxid:zxid:0.7
  • cpe:2.3:a:zxid:zxid:0.8
    cpe:2.3:a:zxid:zxid:0.8
  • cpe:2.3:a:zxid:zxid:0.9
    cpe:2.3:a:zxid:zxid:0.9
  • cpe:2.3:a:zxid:zxid:0.10
    cpe:2.3:a:zxid:zxid:0.10
  • cpe:2.3:a:zxid:zxid:0.11
    cpe:2.3:a:zxid:zxid:0.11
  • cpe:2.3:a:zxid:zxid:0.12
    cpe:2.3:a:zxid:zxid:0.12
  • cpe:2.3:a:zxid:zxid:0.13
    cpe:2.3:a:zxid:zxid:0.13
  • cpe:2.3:a:zxid:zxid:0.14
    cpe:2.3:a:zxid:zxid:0.14
  • cpe:2.3:a:zxid:zxid:0.15
    cpe:2.3:a:zxid:zxid:0.15
  • cpe:2.3:a:zxid:zxid:0.16
    cpe:2.3:a:zxid:zxid:0.16
  • cpe:2.3:a:zxid:zxid:0.17
    cpe:2.3:a:zxid:zxid:0.17
  • cpe:2.3:a:zxid:zxid:0.18
    cpe:2.3:a:zxid:zxid:0.18
  • cpe:2.3:a:zxid:zxid:0.19
    cpe:2.3:a:zxid:zxid:0.19
  • cpe:2.3:a:zxid:zxid:0.20
    cpe:2.3:a:zxid:zxid:0.20
  • cpe:2.3:a:zxid:zxid:0.21
    cpe:2.3:a:zxid:zxid:0.21
  • cpe:2.3:a:zxid:zxid:0.22
    cpe:2.3:a:zxid:zxid:0.22
  • cpe:2.3:a:zxid:zxid:0.25
    cpe:2.3:a:zxid:zxid:0.25
  • cpe:2.3:a:zxid:zxid:0.26
    cpe:2.3:a:zxid:zxid:0.26
  • cpe:2.3:a:zxid:zxid:0.27
    cpe:2.3:a:zxid:zxid:0.27
  • cpe:2.3:a:zxid:zxid:0.28
    cpe:2.3:a:zxid:zxid:0.28
  • cpe:2.3:a:zxid:zxid:0.29
    cpe:2.3:a:zxid:zxid:0.29
CVSS
Base: 5.0 (as of 07-01-2009 - 17:28)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS9_112837.NASL
    description SunOS 5.9: in.dhcpd libresolv and BIND9 pa. Date this patch was last updated by Sun : Jul/21/11
    last seen 2018-09-02
    modified 2016-12-12
    plugin id 26165
    published 2007-09-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=26165
    title Solaris 9 (sparc) : 112837-24
  • NASL family VMware ESX Local Security Checks
    NASL id VMWARE_VMSA-2009-0004.NASL
    description a. Updated OpenSSL package for the Service Console fixes a security issue. OpenSSL 0.9.7a-33.24 and earlier does not properly check the return value from the EVP_VerifyFinal function, which could allow a remote attacker to bypass validation of the certificate chain via a malformed SSL/TLS signature for DSA and ECDSA keys. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-5077 to this issue. b. Update bind package for the Service Console fixes a security issue. A flaw was discovered in the way Berkeley Internet Name Domain (BIND) checked the return value of the OpenSSL DSA_do_verify function. On systems using DNSSEC, a malicious zone could present a malformed DSA certificate and bypass proper certificate validation, allowing spoofing attacks. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-0025 to this issue. c. Updated vim package for the Service Console addresses several security issues. Several input flaws were found in Visual editor IMproved's (Vim) keyword and tag handling. If Vim looked up a document's maliciously crafted tag or keyword, it was possible to execute arbitrary code as the user running Vim. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-4101 to this issue. A heap-based overflow flaw was discovered in Vim's expansion of file name patterns with shell wildcards. An attacker could create a specially crafted file or directory name, when opened by Vim causes the application to stop responding or execute arbitrary code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-3432 to this issue. Several input flaws were found in various Vim system functions. If a user opened a specially crafted file, it was possible to execute arbitrary code as the user running Vim. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-2712 to this issue. A format string flaw was discovered in Vim's help tag processor. If a user was tricked into executing the 'helptags' command on malicious data, arbitrary code could be executed with the permissions of the user running VIM. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2007-2953 to this issue.
    last seen 2019-01-16
    modified 2018-08-06
    plugin id 40389
    published 2009-07-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=40389
    title VMSA-2009-0004 : ESX Service Console updates for openssl, bind, and vim
  • NASL family Solaris Local Security Checks
    NASL id SOLARIS9_X86_114265.NASL
    description SunOS 5.9_x86: in.dhcpd libresolv and BIND. Date this patch was last updated by Sun : Jul/21/11
    last seen 2018-09-01
    modified 2016-12-12
    plugin id 27094
    published 2007-10-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=27094
    title Solaris 9 (x86) : 114265-23
refmap via4
bugtraq 20090107 [oCERT-2008-016] Multiple OpenSSL signature verification API misuses
misc http://www.ocert.org/advisories/ocert-2008-016.html
xf openssl-dsa-verify-security-bypass(47837)
Last major update 12-07-2013 - 00:00
Published 07-01-2009 - 13:30
Last modified 11-10-2018 - 16:59
Back to Top