Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-43668 is a critical-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Apache Inlong. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-43668 is an Authorization Bypass Through User-Controlled Key vulnerability (CWE-639) affecting Apache InLong versions 1.4.0 through 1.8.0. The flaw allows certain sensitive parameter checks, including those for "autoDeserialize" and "allowLoadLocalInfile", to be bypassed when keys are supplied by the user.
An unauthenticated remote attacker can supply crafted keys to evade authorization controls, potentially achieving full compromise of confidentiality, integrity, and availability on the affected InLong instance. The vulnerability carries a CVSS 3.1 score of 9.8, reflecting network-accessible exploitation without credentials or user interaction.
Apache advisories recommend upgrading to version 1.9.0 or applying the fix from pull request 8604 to restore proper validation of the affected parameters.
EPSS for this CVE rose from a low baseline to a peak of 0.0518 on 2025-01-22 before receding to the current value of 0.0006, indicating a period of increased exploitation interest after public disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2805
Vulnerability Data
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…
more
solve it. [1] https://github.com/apache/inlong/pull/8604
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.
Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing authorization checks but does not prevent the weakness in production.
Information access restriction explicitly enforces that users may only retrieve data they are authorized to see, directly addressing user-controlled key bypass.
Access control policy directly requires enforcement of authorization rules that prevent unauthorized access via manipulated keys.
Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.
Privileged access rights control restricts what data each user may access, mitigating direct object reference attacks.
Secure development lifecycle includes authorization design but does not itself implement runtime access checks.