ID CVE-2009-0591
Summary The CMS_verify function in OpenSSL 0.9.8h through 0.9.8j, when CMS is enabled, does not properly handle errors associated with malformed signed attributes, which allows remote attackers to repudiate a signature that originally appeared to be valid but was actually invalid.
References
Vulnerable Configurations
  • OpenSSL Project OpenSSL 0.9.8h
    cpe:2.3:a:openssl:openssl:0.9.8h
  • OpenSSL Project OpenSSL 0.9.8i
    cpe:2.3:a:openssl:openssl:0.9.8i
  • OpenSSL Project OpenSSL 0.9.8j
    cpe:2.3:a:openssl:openssl:0.9.8j
CVSS
Base: 2.6 (as of 27-03-2009 - 13:37)
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 HIGH NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
nessus via4
  • NASL family Web Servers
    NASL id OPENSSL_0_9_8K_CMS.NASL
    description According to its banner, the remote server is running a version of OpenSSL that is earlier than 0.9.8k. As such, it may allow a valid sign to generate invalid signatures which would appear valid and could be repudiated later. This only affects CMS users. CMS appeared in OpenSSL 0.9.8h.
    last seen 2019-02-21
    modified 2018-07-16
    plugin id 17764
    published 2012-01-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=17764
    title OpenSSL < 0.9.8k Signature Repudiation
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2009-005.NASL
    description The remote host is running a version of Mac OS X 10.5 or 10.4 that does not have Security Update 2009-005 applied. This security update contains fixes for the following products : - Alias Manager - CarbonCore - ClamAV - ColorSync - CoreGraphics - CUPS - Flash Player plug-in - ImageIO - Launch Services - MySQL - PHP - SMB - Wiki Server
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 40945
    published 2009-09-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=40945
    title Mac OS X Multiple Vulnerabilities (Security Update 2009-005)
  • NASL family Web Servers
    NASL id OPENSSL_0_9_8K.NASL
    description According to its banner, the remote server is running a version of OpenSSL prior to 0.9.8k. It is, therefore, affected by multiple vulnerabilities : - A denial of service vulnerability exists in the ASN1_STRING_print_ex() function due to improper string handling. A remote attacker can exploit this to cause an invalid memory access and application crash. (CVE-2009-0590) - A flaw exists in the CMS_verify() function due to improper handling of errors associated with malformed signed attributes. A remote attacker can exploit this to repudiate a signature that originally appeared to be valid but was actually invalid. (CVE-2009-0591) - A denial of service vulnerability exists due to improper handling of malformed ASN.1 structures. A remote attacker can exploit this to cause an invalid memory access and application crash. (CVE-2009-0789) - A memory leak exists in the SSL_free() function in ssl_lib.c. A remote attacker can exploit this to exhaust memory resources, resulting in a denial of service condition. (CVE-2009-5146)
    last seen 2019-02-21
    modified 2018-07-16
    plugin id 17763
    published 2012-01-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=17763
    title OpenSSL < 0.9.8k Multiple Vulnerabilities
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_1_LIBOPENSSL-DEVEL-090415.NASL
    description This update of openssl fixes the following problems : - CVE-2009-0590: ASN1_STRING_print_ex() function allows remote denial of service - CVE-2009-0591: CMS_verify() function allows signatures to look valid - CVE-2009-0789: denial of service due to malformed ASN.1 structures
    last seen 2019-02-21
    modified 2016-12-21
    plugin id 40260
    published 2009-07-21
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=40260
    title openSUSE Security Update : libopenssl-devel (libopenssl-devel-786)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_LIBOPENSSL-DEVEL-090415.NASL
    description This update of openssl fixes the following problems : - ASN1_STRING_print_ex() function allows remote denial of service. (CVE-2009-0590) - CMS_verify() function allows signatures to look valid. (CVE-2009-0591) - denial of service due to malformed ASN.1 structures. (CVE-2009-0789)
    last seen 2019-02-21
    modified 2016-12-21
    plugin id 41423
    published 2009-09-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=41423
    title SuSE 11 Security Update : OpenSSL (SAT Patch Number 772)
  • NASL family Slackware Local Security Checks
    NASL id SLACKWARE_SSA_2009-098-01.NASL
    description New openssl packages are available for Slackware 11.0, 12.0, 12.1, 12.2, and -current to fix security issues.
    last seen 2019-02-21
    modified 2018-08-09
    plugin id 36104
    published 2009-04-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=36104
    title Slackware 11.0 / 12.0 / 12.1 / 12.2 / current : openssl (SSA:2009-098-01)
refmap via4
apple APPLE-SA-2009-09-10-2
bid 34256
confirm
hp
  • HPSBOV02540
  • HPSBUX02435
  • SSRT090059
netbsd NetBSD-SA2009-008
osvdb 52865
sectrack 1021907
secunia
  • 34411
  • 34460
  • 34666
  • 35065
  • 35380
  • 35729
  • 36701
  • 42724
  • 42733
suse SUSE-SR:2009:010
vupen
  • ADV-2009-0850
  • ADV-2009-1020
  • ADV-2009-1175
  • ADV-2009-1548
xf openssl-cmsverify-security-bypass(49432)
statements via4
contributor Tomas Hoger
lastmodified 2009-03-30
organization Red Hat
statement Not vulnerable. This issue affected OpenSSL CMS functionality which is not present in the openssl packages as shipped with Red Hat Enterprise Linux 2.1, 3, 4 or 5.
Last major update 22-08-2016 - 21:59
Published 27-03-2009 - 12:30
Last modified 16-08-2017 - 21:29
Back to Top