CVE-2023-43666 json
Apache InLong: General user Unauthorized access User Management
published 3y ago modified 4mo ago also GHSA-wj6q-chpv-mcrx , EUVD-2023-2829
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
Insufficient Verification of Data Authenticity vulnerability in Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.8.0,
General user can view all user data like Admin account.
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/8623
Patch / fix
- maven org.apache.inlong:inlong 1.9.0
- github.com/apache/inlong#8623 pull request
- lists.apache.org/thread/scbgh3ty3xcxm3q33r2t9f42gwwo1why advisory
Is CVE-2023-43666 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.inlong:inlong | >=1.4.0, <1.9.0 |
1.9.0 |
Affected products
- Apache Software Foundation Apache InLong
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
lists.apache.org
/thread/scbgh3ty3xcxm3q33r2t9f42gwwo1why
vendor-advisory, web, mailing-list, patch
-
github.com
/apache/inlong/pull/8623
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-43666
advisory
Sources
- CVE List CVE-2023-43666
- GitHub Advisory GHSA-wj6q-chpv-mcrx
- NVD CVE-2023-43666
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.