Update: The information displayed on Aladdin blog post is erroneous, the end-user is able to extract the file. Still working with Aladdin on the issue



Release mode: Forced release, vendor has not replied.

Ref : TZO-152009 - Aladdin eSafe Generic Evasion
Status : Not patched
Vendor : http://www.aladdin.com
Security notification reaction rating : Catastrophic
(vendor visited specific url at my website but has not reacted)

Disclosure Policy :
http://blog.zoller.lu/2008/09/notification-and-disclosure-policy.html

Affected products :
- t.b.a (Vendor has not reacted, please see below)
- probably all versions including gateway solutions

As this bug has not been reproduced by the vendor, this limited advisory relies on the assumption that my tests were conclusive and that the test environment mimics the production environment.

I. Background
Quote: "Aladdin is dedicated to being the leading provider of security services and solutions used to protect digital assets, enable secure business, and maximize the benefits from creating, selling, distributing and using digital content."


II. Description
The parsing engine can be bypassed by a specially crafted and formatted archive file. Details are currently withheld due to other vendors that are in process of deploying patches.

A professional reaction to a vulnerability notification is a way to measure the maturity of a vendor in terms of security. Aladdin is given a grace period of two (2) weeks to reply to my notification. Failure to do so will result in POC being released in two (2) weeks.

Aladdin is advised to leave a specific security contact at [1] in order to simplify getting in contact with them.

As this bug has not been reproduced by the vendor, this limited advisory relies on the assumption that my tests were conclusive.

III. Impact
A general description of the impact and nature of AV Bypasses/evasions can be read at : http://blog.zoller.lu/2009/04/case-for-av-bypassesevasions.html

The bug results in denying the engine the possibility to inspect code within the archive. There is no inspection of the content at all.


IV. Disclosure timeline
DD/MM/YYYY
  • 04/04/2009 : Send proof of concept, description the terms under which I cooperate and the planned disclosure date. There is no security adress listed at [1] and hence took previously known security contacts that are known to exist.
No reply.

  • 13/04/2009 : Resending. Copied security@aladdin.de, security@aladdin.com secure@aladdin.com, secure@aladdin.de,support@aladdin.com, support@aladdin.de in CC.
No reply.

  • 16/04/2009 : Resending specifying this is the last attempt to disclose reponsibly.
No reply.

  • 18/04/2009 : Online virus scan service offered to bridge the gap between AV vendors that don't reply and myself. Aladdin was contacted through this third party.
No reaction

No reaction
  • 27/04/2009 : Release of this limited advisory and begin of grace period.

  • 27/04/2009 : Aladdin got in contact and are already working on the issue


[1] http://osvdb.org/vendor/1/Aladdin%20Knowledge%20Systems

1 comments

chr1x said... @ 30 August, 2009 20:39

It's funny in how some vendors just are afraid when a vulnerability is discovered.

Post a Comment