Skip to content
Fencer Intel
critical 9.8

CVE-2023-43668 json

Apache InLong: Jdbc Connection Security Bypass in InLong

published 3y ago modified 4mo ago also GHSA-rp6x-ggw6-8g56 , EUVD-2023-2805

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

Authorization Bypass Through User-Controlled Key vulnerability in Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.8.0,

some sensitive params checks will be bypassed, like "autoDeserizalize","allowLoadLocalInfile"....

.

Users are advised to upgrade to Apache InLong's 1.9.0 or cherry-pick [1] to solve it.

[1]  https://github.com/apache/inlong/pull/8604

Patch / fix

  • maven org.apache.inlong:manager-pojo 1.9.0
  • apache inlong 1.8.0

Is CVE-2023-43668 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.inlong:manager-pojo
>=1.4.0, <1.9.0
1.9.0

Affected products

  • Apache Software Foundation Apache InLong
  • apache inlong

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.