Portcullis Advisory 05-001 Update, Webseries Payment Application

From: Paul J Docherty (PJD_at_portcullis-security.com)
Date: 02/02/05

  • Next message: Paul J Docherty: "Portcullis Advisory 05-006 Update, Webseries Payment Application"
    Date: Wed, 2 Feb 2005 18:07:11 -0000
    To: "bugs" <bugs@securitytracker.com>, "Bugtraq" <bugtraq@securityfocus.com>, "secunia" <vuln@secunia.com>
    
    

    Portcullis Security Advisory

    AREAS UPDATED: VENDOR RESPONSE - IMPACT.

    VENDOR RESPONSE:

    The product vendor, Bottomline Technologies has provided Portcullis with
    the following response to the security advisory. It should be noted that
    the resolution of this issue has not been verified by Portcullis:

    Bottomline acknowledge that there is a theoretical threat to the system
    via this vulnerability, however would point out it would require two
    trusted users to collude in order for any changes to take affect and
    both would need a good understanding of the software beyond that usually
    available to the end users. This of course does not take into account
    any of the customers' internal security processes and procedures, which
    would typically surround the use of any sensitive software.

    In order to further enhance the security of the system a service pack
    will be released in Q1 2005, which will check entitlements prior to
    invoking any user function. If the user does not have existing
    entitlements to that function, an error message will be logged and the
    user will be logged off and disabled until re-enabled.

    Contact Bottomline at: support@bottomline.co.uk Tel: +44 (0)1189
    258253.

    Vulnerable System:

    Webseries Payment Application
     
    Vulnerability Title:
     
    Lack of Backend Authorisation Checking
     
    Vulnerability discovery and development:
     
    Portcullis Security Testing Services
     
    Affected systems:
     
    Bottomline Webseries Payment Application
     
    Details:
     
    Portcullis consultants discovered that although privileged operations
    are
    not displayed in the application menu presented to unprivileged users,
    these
    operations may still be executed by directly accessing the appropriate
    URL.
     
    This, in effect, means that the core application is not carrying out any
    form of authorisation verification and that any authenticated user,
    regardless of the rights they have been assigned, can perform any action
    available to any user of the system.
     
    In its simplest form this vulnerability could be used to gather a list
    of
    privileged users by accessing the "User Entitlements" report which
    details
    user's security groups and administrative status. An attacker could use
    this information to greatly increase their likelihood of success in
    gaining
    unauthorised access.
     
    Impact:
     
    An unauthorized user could, by directly accessing the SaveUser.asp
    script create a new user with administrative privileges. IT SHOULD BE
    NOTED THAT ANY NEW USER CREATED WOULD NOT BE ACTIVE UNTIL ANOTHER,
    (DIFFERENT FROM THE CREATOR) PRIVILEDGED ACCOUNT ENABLES THE USER, THE
    NEWLY CREATED ACCOUNT WOUL IN EFFECT BE A GHOST ACCOUNT, HOLDING THE
    PRIVILEDGES BUT INACTIVE.

    Portcullis consultants developed the following simple HTML page to
    perform this action:
     
    Any other system operation including user approval, security group
    modification and payment approval can be performed in a similar manner.
     
    The only thing obstructing a malicious attacker from succeeding in such
    attacks is that the approval system has been correctly implemented.
    Even by
    accessing URLs directly, a user cannot approve their own changes.
     
    Two unprivileged users, acting in collusion, have the ability to execute
    any
    function the system is capable of performing. This includes submitting,
    and
    approving, payments of unlimited value.
     
    Exploit:
    Portcullis consultants developed the following simple HTML page to
    perform this action:
     
    <html>
      <body>
      <h1>Add User</h1>
      <hr>
      <form action="http://target/wsapp/SaveUser.asp" method="post">
      Action <input name="Action" value="ADD" type="text"><br>
      UserID <input type="text" name="UserID"><br>
      UserName <input type="text" name="UserName"><br>
      Password 1 <input type="text" name="Password1"><br>
      Password 2 <input type="text" name="Password2"><br>
      Email <input type="text" name="EMail"><br>
      Administrator <input type="checkbox" name=Admin value=1><br>
      Application User <input type="checkbox" name=AppUser value=1><br>
      User Group <input type="text" name="SelUserGroup" value="111" ><br>
      Security Group <input type="text" name="SecurityGroup"
    value="RegMgr"><br>
      <input type="submit" value="submit">
      </form>
      </html>

    Copyright:
     
    Copyright (c) Portcullis Computer Security Limited 2005, All rights
    reserved worldwide. Permission is hereby granted for the electronic
    redistribution of this information. It is not to be edited or altered in
    any way without the express written consent of Portcullis Computer
    Security Limited.
     
    Disclaimer:
     
    The information herein contained may change without notice. Use of this
    information constitutes acceptance for use in an AS IS condition. There
    are NO warranties, implied or otherwise, with regard to this information
    or its use. Any use of this information is at the user's risk. In no
    event shall the author/distributor (Portcullis Computer Security
    Limited) be held liable for any damages whatsoever arising out of or in
    connection with the use or spread of this information.

    *************************************************************
    The information in this email is confidential and may be
    legally privileged. It is intended solely for the addressee.
    Any opinions expressed are those of the individual and do not
    represent the opinion of the organisation.
    Access to this email by persons other than the intended
    recipient is strictly prohibited.
    If you are not the intended recipient, any disclosure, copying,
    distribution or other action taken or omitted to be taken in
    reliance on it, is prohibited and may be unlawful.
    When addressed to our clients any opinions or advice contained
    in this email is subject to the terms and conditions expressed
    in the applicable Portcullis Computer Security Limited terms
    of business.
    **************************************************************


  • Next message: Paul J Docherty: "Portcullis Advisory 05-006 Update, Webseries Payment Application"

    Relevant Pages

    • Portcullis Advisory 05-006 Update, Webseries Payment Application
      ... Portcullis Security Advisory ... Bottomline acknowledge that there is a slight risk of exposure of data ... via unauthorised report generation. ...
      (Bugtraq)
    • Portcullis Advisory 05-007 Update, Webseries Payment Application
      ... Portcullis Security Advisory ... Bottomline believe that this is a low priority, ... Password Policy Implemented At Client rather than Server ...
      (Bugtraq)
    • Portcullis Advisory 05-005 Update, Webseries Payment Application
      ... Portcullis Security Advisory ... AREAS UPDATED: VENDOR RESPONSE. ... Bottomline Webseries Payment Application ...
      (Bugtraq)
    • Re: APACHE$PRIVILEDGED
      ... The primary security on OpenVMS and on most other multi-processing operating systems is implemented via the memory management system and via what VAX calls the change-mode routines, via the Alpha SRM PALcode change-mode equivalent, or via what the IA-32 and IA-32e architectures refer to as the call gate. ... With OpenVMS constructs including device drivers )and user-written system services (UWSS; also known as privileged shareable images), these constructs operate in inner processor modes. ... One of the more hazardous situations for system security is a mixed environment; where there are resources shared between trusted and untrusted environments. ... Not only will the operation that requires privileges now be permitted, but other and potentially unintended operations can also be permitted. ...
      (comp.os.vms)
    • [UNIX] Bugzilla Multiple Vulnerabilities (SQL Injections, Privileges Escalation, Information Leak)
      ... Get your security news from a reliable source. ... user may retain privileges that should have been removed, ... Reference: ... secure bug, you can access the summary of that bug even if you do not have ...
      (Securiteam)