SQL Injection vulnerability in textMessage parameter in /src/chatbotapp/chatWindow.java in wliang6 ChatEngine v.1.0, allows attackers to gain sensitive information.

*   *   Actions
        
        Automate any workflow
        
    *   Packages
        
        Host and manage packages
        
    *   Security
        
        Find and fix vulnerabilities
        
    *   Codespaces
        
        Instant dev environments
        
    *   Copilot
        
        Write better code with AI
        
    *   Code review
        
        Manage code changes
        
    *   Issues
        
        Plan and track work
        
    *   Discussions
        
        Collaborate outside of code
        
    

*   *   GitHub Sponsors
        
        Fund open source developers
        
    
    *   The ReadME Project
        
        GitHub community articles
        
    
*   Pricing

**Search code, repositories, users, issues, pull requests...**

**Provide feedback**

**Saved searches****Use saved searches to filter your results more quickly**

Sign up

CVE-2023-30325: ChatEngine/src/chatbotapp/chatWindow.java at fded8e710ad59f816867ad47d7fc4862f6502f3e · wliang6/ChatEngine

SQL Injection vulnerability in username field in /src/chatbotapp/chatWindow.java in Payatu ChatEngine v.1.0, allows attackers to gain sensitive information.

CVE-2023-30323: ChatEngine/src/chatbotapp/chatWindow.java at fded8e710ad59f816867ad47d7fc4862f6502f3e · wliang6/ChatEngine

Cross Site Scripting (XSS) vulnerability in username field in /src/chatbotapp/chatWindow.java in Payatu ChatEngine v.1.0, allows attackers to execute arbitrary code.

Web Application Security

Mobile application Security

IoT Product Ecosystem Security

Red Team Assessment

Cloud Application and Infrastructure Security

Code Review

Threat Modeling and Architecture Review

Product Security Assurance Programme

Cyber Investigation and Forensic

Critical Infrastructure Security Assessment

Blockchain Security Audit

Other Cyber Security Services

CVE-2023-30322: Cross Site Scripting (XSS) in username field in chatWindow functionality in ChatEngine 1.0 - Payatu

A stored cross-site scripting (XSS) vulnerability in the custom variables module of eyoucms v1.6.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

**Stored XSS exists in version 1.6.3, which can lead to stealing sensitive information of logged-in users**

A bug was found. stored xss vulnerability exists.  
Only test in the test environment, do not do any illegal operations, now the bug feedback to the manufacturer.  
Software Link :https://github.com/weng-xianhu/eyoucms  
Website : http://www.eyoucms.com/

**Insert the poc into the custom variables module of the background system**  
**Here you can fill in malicious JavaScript code to cause stored xss**

  

**Causes stored XSS to steal sensitive information of logged-in users**  

Poc:<img src=a onerror=alert(1)>

CVE-2023-37132: Stored XSS exists in version 1.6.3, which can lead to stealing sensitive information of logged-in users · Issue #45 · weng-xianhu/eyoucms

A stored cross-site scripting (XSS) vulnerability in the Image Upload module of eyoucms v1.6.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

**EyouCMS V1.6.3 "Image Upload" module has cross-site storage vulnerability**  
A bug was found. stored xss vulnerability exists.  
Only test in the test environment, do not do any illegal operations, now the bug feedback to the manufacturer.  
Software Link :https://github.com/weng-xianhu/eyoucms  
Website : http://www.eyoucms.com/

**Insert the poc into the picture upload module of the background system to modify the grouping information  
Here you can fill in malicious JavaScript code to cause stored xss**  
  
  
**Causes stored XSS to steal sensitive information of logged-in users**  

Poc:<img src=a onerror=alert('xss')>

CVE-2023-37135: EyouCMS V1.6.3 "Image Upload" module has cross-site storage vulnerability · Issue #48 · weng-xianhu/eyoucms

A stored cross-site scripting (XSS) vulnerability in the Basic Website Information module of eyoucms v1.6.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

**EyouCMS V1.6.3 "Basic Website Information" module has cross-site storage vulnerability**  
A bug was found. stored xss vulnerability exists.  
Only test in the test environment, do not do any illegal operations, now the bug feedback to the manufacturer  
Software Link :https://github.com/weng-xianhu/eyoucms  
Website : http://www.eyoucms.com/

**If you insert the poc into the Basic Information module of the background system and execute the poc script, xss attacks will occur  
Here you can fill in malicious JavaScript code to cause stored xss**  
  
**Causes stored XSS to steal sensitive information of logged-in users**  

Poc: <script>alert("xss")</script>

CVE-2023-37136: EyouCMS V1.6.3 "Basic Website Information" module has cross-site storage vulnerability · Issue #49 · weng-xianhu/eyoucms

A stored cross-site scripting (XSS) vulnerability in the Column management module of eyoucms v1.6.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

**The "Column management" module of eyoucms1.6.3 has a storage XSS vulnerability**  
A bug was found. stored xss vulnerability exists.  
Only test in the test environment, do not do any illegal operations, now the bug feedback to the manufacturer.  
Software Link :https://github.com/weng-xianhu/eyoucms  
Website : http://www.eyoucms.com/

**Insert poc into the "Column management" module of the background system  
Here you can fill in malicious JavaScript code to cause stored xss**  
  
  
**Causes stored XSS to steal sensitive information of logged-in users**  

Poc:<svg/onload=alert("xss")>

CVE-2023-37133: The "Column management" module of eyoucms1.6.3 has a storage XSS vulnerability · Issue #46 · weng-xianhu/eyoucms

A stored cross-site scripting (XSS) vulnerability in the Basic Information module of eyoucms v1.6.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.

**EyouCMS V1.6.3 "Basic Information" module has a storage cross-site vulnerability**  
A bug was found. stored xss vulnerability exists.  
Only test in the test environment, do not do any illegal operations, now the bug feedback to the manufacturer  
Software Link :https://github.com/weng-xianhu/eyoucms  
Website : http://www.eyoucms.com/

**Insert the poc into the website information module of the background system  
Here you can fill in malicious JavaScript code to cause stored xss**  
  
  
**Causes stored XSS to steal sensitive information of logged-in users**  

Poc:<svg/onload=alert("xss")>

CVE-2023-37134: EyouCMS V1.6.3 "Basic Information" module has a storage cross-site vulnerability · Issue #47 · weng-xianhu/eyoucms

Cross-site scripting (xss) vulnerabilities exist in the requestHandlers.js detail_device functionality of Milesight VPN v2.0.2. A specially-crafted HTTP request can lead to arbitrary Javascript code injection. An attacker can send an HTTP request to trigger these vulnerabilities.This XSS is exploited through the remote_subnet field of the database

**SUMMARY**

Cross-site scripting (xss) vulnerabilities exist in the requestHandlers.js detail\_device functionality of Milesight VPN v2.0.2. A specially-crafted HTTP request can lead to arbitrary Javascript code injection. An attacker can send an HTTP request to trigger these vulnerabilities.

**CONFIRMED VULNERABLE VERSIONS**

The versions below were either tested or verified to be vulnerable by Talos or confirmed to be vulnerable by the vendor.

Milesight VPN v2.0.2

**PRODUCT URLS**

MilesightVPN - https://www.milesight-iot.com/milesightvpn/

**CVSSv3 SCORE**

8.3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H 9.6 - CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - chain: TALOS-2023-1702  
\##### CWE

CWE-80 - Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

**DETAILS**

The MilesightVPN is a software that make easier the setup of VPN tunnel for the Milesight products and allow to monitor the connection status with a web server interface.

The MilesightVPN exposes the /Device_Auth API used to authenticate to the server and to get the an OpenVPN configuration file. This API is for the various Milesight devices, the API requires as data the serial number, the authentication code, the device name and the subnet of the device. Essentially the API expects four entries in the POST payload:

*   authcode: is a secret generated by the MilesightVPN
*   subnet: the subnet mask of the main network used by the device
*   device\_name: the identifier of the device that is connecting to the MilesightVPN server
*   sn: is the serial number of the device that is connecting to the MilesightVPN server

After been registered, the device will appear in the Device table showing the provided information. This Device table is in the landing page after the login.

Following the relevant portion of the Embedded JavaScript template related to the device table:

    <table class="table table-no-bordered" data-striped="true" data-height="100%" id="tbl_content" data-toggle="table" data-url="/detail_device" data-target="/detail_device" data-id-field="sn" data-pagination="true" data-sort-stable="true" data-sort-name="connect_time" data-sort-order="asc" data-toolbar="#deviceToolbar" data-search="true" data-search-on-enter-key="true" data-cache="false">
        <thead>
            <tr>
                <th data-field="name" data-width="15%" data-sortable="true" data-formatter="name_formatter"><%=lang.detail.device.name%></th>
                <th data-field="status" data-width="10%" data-sortable="true" data-formatter="status_formatter"><%=lang.detail.device.status%></th>
                <th data-field="sn" data-width="10%" data-sortable="true"><%=lang.detail.device.sn%></th>
                <th data-field="virtual_ip" data-width="15%" data-sortable="true"><%=lang.detail.device.virtualip%></th>
                <th data-field="real_ip" data-width="15%" data-sortable="true"><%=lang.detail.device.realip%></th>
                <th data-field="remote_subnet" data-width="15%" data-sortable="true" data-formatter="subnet_formatter"><%=lang.detail.device.subnet%></th>
                <th data-field="connect_time" data-width="15%" data-sortable="true" data-formatter="time_formatter"><%=lang.detail.device.time%></th>
                <th data-field="history" data-width="10%" data-formatter="history_formatter"><%=lang.detail.device.history%></th>
            </tr>
        </thead>
    

The data of this table is filled using the requestHandlers.js’s detail_device function:

    function detail_device(res,postdata,connection){
        var $sql="select * from device";
        $sql+=' left join ';
        $sql+=' (select count(*) as total,remote_subnet from device group by remote_subnet) repeatsubnet on repeatsubnet.remote_subnet=device.remote_subnet';
        var result={};
        connection.query($sql).then(function(data){
            if(data['error'])
            {
                res.write(JSON.stringify(result));
                res.end();
            }
            else
            {
                if(data['result'].length>0)
                {
                    result=JSON.stringify(data['result']);
                    res.writeHead(200,{'Content-Type':'application/json','Content-length':Buffer.byteLength(result, 'utf8')});
                    res.write(result);
                    res.end();
                }
                else
                {
                    res.write(JSON.stringify([]));
                    res.end();
                }
            }
        });
    }
    

The device table has the following schema:

    +---------------+--------------+------+-----+---------+-------+
    | Field         | Type         | Null | Key | Default | Extra |
    +---------------+--------------+------+-----+---------+-------+
    | name          | varchar(255) | YES  |     | NULL    |       |
    | sn            | varchar(12)  | NO   | PRI | NULL    |       |
    | virtual_ip    | varchar(15)  | YES  |     | NULL    |       |
    | real_ip       | varchar(32)  | YES  |     | NULL    |       |
    | remote_subnet | varchar(32)  | YES  |     | NULL    |       |
    | connect_time  | int          | YES  |     | NULL    |       |
    | status        | int          | YES  |     | NULL    |       |
    +---------------+--------------+------+-----+---------+-------+ The `device` table is populated through the registered devices, so through the `/Device_Auth` API.
    

From when a Milesight device is registered, using the /Device_Auth API, until showing its data in the web interface, no checks about the data are performed, this can lead an XSS vulnerability. An attacker can upload malicious Javascript code through the /Device_Auth API, registering a device. An admin of the server would execute this malicious javascript whenever they viewed the details page due to the stored XSS. An attacker would need to know the Authorization Code of the server to actually use the /Device_Auth API. But because TALOS-2023-1702 this information can be easily retrieved by an attacker.

**CVE-2023-24496 - XSS in the name field**

An attacker can upload malicious Javascript code through the /Device_Auth’s device_name parameter. The device_name value will be stored in the device database as the name field.

**CVE-2023-24497 - XSS in the remote\_subnet field**

An attacker can upload malicious Javascript code through the /Device_Auth’s subnet parameter. The subnet value will be stored in the device database as the remote_subnet field.

**VENDOR RESPONSE**

Since the maintainer of this software did not release a patch during the 90 day window specified in our policy, we have now decided to release the information regarding this vulnerability, to make users of the software aware of this problem. See Cisco’s Coordinated Vulnerability Disclosure Policy for more information: https://tools.cisco.com/security/center/resources/vendor\_vulnerability\_policy.html

**TIMELINE**

2023-02-14 - Initial Vendor Contact  
2023-02-21 - Vendor Disclosure  
2023-07-06 - Public Release

Discovered by Francesco Benvenuto of Cisco Talos.

CVE-2023-24497: TALOS-2023-1704 || Cisco Talos Intelligence Group

Red Hat Security Advisory 2023-3915-01 - Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution designed for on-premise or private cloud deployments. This advisory contains the container images for Red Hat OpenShift Container Platform 4.11.44.

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA256

=====================================================================  
                   Red Hat Security Advisory

Synopsis:          Important: OpenShift Container Platform 4.11.44 bug fix and security update  
Advisory ID:       RHSA-2023:3915-01  
Product:           Red Hat OpenShift Enterprise  
Advisory URL:      https://access.redhat.com/errata/RHSA-2023:3915  
Issue date:        2023-07-06  
CVE Names:         CVE-2022-2879 CVE-2022-2880 CVE-2022-2995   
                   CVE-2022-27664 CVE-2022-32149 CVE-2022-32190   
                   CVE-2022-41715 CVE-2023-1370 CVE-2023-3089   
                   CVE-2023-24329 CVE-2023-24540 CVE-2023-32067   
=====================================================================

1. Summary:

Red Hat OpenShift Container Platform release 4.11.44 is now available with  
updates to packages and images that fix several bugs and add enhancements.

This release includes a security update for Red Hat OpenShift Container  
Platform 4.11.

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.

2. Description:

Red Hat OpenShift Container Platform is Red Hat's cloud computing  
Kubernetes application platform solution designed for on-premise or private  
cloud deployments.

This advisory contains the container images for Red Hat OpenShift Container  
Platform 4.11.44. See the following advisory for the RPM packages for this  
release:

https://access.redhat.com/errata/RHSA-2023:3914

Space precludes documenting all of the container images in this advisory.  
See the following Release Notes documentation, which will be updated  
shortly for this release, for details about these changes:

https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.html

Security Fix(es):  
* golang: html/template: improper handling of JavaScript whitespace  
(CVE-2023-24540)

* openshift: OCP does not use FIPS-certified cryptography (CVE-2023-3089)

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.

All OpenShift Container Platform 4.11 users are advised to upgrade to these  
updated packages and images when they are available in the appropriate  
release channel. To check for available updates, use the OpenShift CLI (oc)  
or web console. Instructions for upgrading a cluster are available at  
https://docs.openshift.com/container-platform/4.11/updating/updating-cluster-cli.html

3. Solution:

For OpenShift Container Platform 4.11 see the following documentation,  
which will be updated shortly for this release, for important instructions  
on how to upgrade your cluster and fully apply this asynchronous errata  
update:

https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.html

You may download the oc tool and use it to inspect release image metadata  
for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests  
may be found at  
https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags.

    The sha values for the release are

    (For x86_64 architecture)  
The image digest is  
sha256:52cbfbbeb9cc03b49c2788ac7333e63d3dae14673e01a9d8e59270f3a8390ed3

    (For s390x architecture)  
The image digest is  
sha256:8e25fe8123b744a1e7ae48b1d02cb989387168c6bc3eef8a47ee7ee13157c25f

    (For ppc64le architecture)  
The image digest is  
sha256:9d9ee02572038ccc4750e416c2acb4a222bfc4fcca63a3595ff63685304d0e53

    (For aarch64 architecture)  
The image digest is  
sha256:e26acde99c69074890e2eefc4ca89506e3dd7426c049a7ff02734cabfa3be42a

All OpenShift Container Platform 4.11 users are advised to upgrade to these  
updated packages and images when they are available in the appropriate  
release channel. To check for available updates, use the OpenShift CLI (oc)  
or web console. Instructions for upgrading a cluster are available at  
https://docs.openshift.com/container-platform/4.11/updating/updating-cluster-cli.html

4. Bugs fixed (https://bugzilla.redhat.com/):

2196027 - CVE-2023-24540 golang: html/template: improper handling of JavaScript whitespace  
2212085 - CVE-2023-3089 openshift: OCP & FIPS mode

5. JIRA issues fixed (https://issues.redhat.com/):

OCPBUGS-14004 - "pipelines-as-code-pipelinerun-go" configMap is not been used for the Go repository   
OCPBUGS-14355 - [4.11.z] [GCP] worker node with Sriov operator installed fails to come up online after reboot  
OCPBUGS-14413 - "Create" button inactive when creating application with "Import from Git" workflow  
OCPBUGS-14456 - CRL configmap is limited by 1MB max, not allowing for multiple public CRLS. (4.11)  
OCPBUGS-14457 - mtls CRL not working when using an intermediate CA (4.11)  
OCPBUGS-14654 - [4.11] IPI redfish installation fails on inspect for EthernetInterfaces  
OCPBUGS-14686 - Package openvswitch2.17 conflicts with openvswitch2.15 during the 4.12 to 4.13 upgrade of RHEL worker  
OCPBUGS-14746 - container_network* metrics stop reporting after container restart  
OCPBUGS-14931 - kuryr-controller crashes on KuryrPort cleanup when subport is already gone: Request requires an ID but none was found  
OCPBUGS-15150 - TestNewApp unit tests in oc are failing  
OCPBUGS-15151 - e2e-agnostic-ovn-cmd is permanently failing due to registry.centos.org  
OCPBUGS-15361 - Bump to kubernetes 1.24.15  
OCPBUGS-4812 -  oc new-app command using s2i with private Github repo (over SSH) fails using oc v4.10

6. References:

https://access.redhat.com/security/cve/CVE-2022-2879  
https://access.redhat.com/security/cve/CVE-2022-2880  
https://access.redhat.com/security/cve/CVE-2022-2995  
https://access.redhat.com/security/cve/CVE-2022-27664  
https://access.redhat.com/security/cve/CVE-2022-32149  
https://access.redhat.com/security/cve/CVE-2022-32190  
https://access.redhat.com/security/cve/CVE-2022-41715  
https://access.redhat.com/security/cve/CVE-2023-1370  
https://access.redhat.com/security/cve/CVE-2023-3089  
https://access.redhat.com/security/cve/CVE-2023-24329  
https://access.redhat.com/security/cve/CVE-2023-24540  
https://access.redhat.com/security/cve/CVE-2023-32067  
https://access.redhat.com/security/updates/classification/#important  
https://access.redhat.com/security/vulnerabilities/RHSB-2023-001

7. Contact:

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

Copyright 2023 Red Hat, Inc.  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1

iQIcBAEBCAAGBQJkpj2NAAoJENzjgjWX9erEfG8P/05BRiaqdCD1dgYerHwb64ms  
O9YCegBzmBdVkjzSCRiTU/x/Mn5PP69KMjMuxwusL1NKsp5eh8Z3hUtHCQUyOsyE  
zvQnO+ktOs0QYI7tzGd3Nj22o3xpJnXXbr+dGA+M97IXBA0Zb4xz3BlF11ahdPnR  
7jz1dhd3KBds/w/ebbtHdQspoyAWCRhB+/Mtz6bamJg4sGiqETlPsPD5Vp9+RgHC  
SFKc8+uPuGJy2vTdeo9O3rITFCbggT21zli7A9eGlS2/LgV+B/NbK7fdNzHsiHIg  
Xy4Dl6KFpGwuKjYsblsNNnViSmSRarJ4IurU4DzLeNyBFAoWpmdGjiOV3jM+9BYZ  
gKV3yzM5xkm9o1J3RC+b/TPZeWYHZn/OHdf7gfS1LmMmw48CV2sFWZb18w6U1kM3  
wvOEffOGIMoQLc3fTJ81nen44WrWUNRdUgOk6QQDiZh1LvhP7Oip9L5abSaufzKP  
lK1JP2M/Rf0chImpV6FhkVRcEpeg8mG1MyQDxdhCRJPAraF6UnxnsETIemII2Z3O  
VJe5/kB8gpZ/4GmLodoffidIeQqExcrQ5p4qM5pd7t2FiHOQ3D6RLpdm+zQfc2wC  
x44L9J7rlqI/sIBQ4JQ96Vx/COeimXGeUezFIhKroQALKBxEUBroCe3UcwjwzM6g  
MPz/sm7kFJXSbvGqi67w  
=AIL0  
-----END PGP SIGNATURE-----  
--  
RHSA-announce mailing list  
RHSA-announce@redhat.com  
https://listman.redhat.com/mailman/listinfo/rhsa-announce

Tag

#java