Security readout for executives and security teams
Plain-English summary
Apache InLong versions 1.1.0 through 1.5.0 contain an unsafe deserialization issue in JDBC connection handling. The published CVSS score is critical because exploitation is described as network-accessible, unauthenticated, and requiring no user interaction, with potential confidentiality, integrity, and availability impact.
Executive priority
Treat this as urgent for any environment using Apache InLong. The risk is critical by CVSS and the vendor identifies a direct upgrade or patch path. If InLong is not deployed, document non-exposure and continue monitoring.
Technical view
CVE-2023-24997 is CWE-502, deserialization of untrusted data, in Apache InLong. The source bundle identifies affected versions as 1.1.0 through 1.5.0 and recommends upgrading to the latest InLong release or cherry-picking Apache PR 7223.
Likely exposure
Organizations are exposed if they run Apache InLong versions 1.1.0 through 1.5.0, especially where InLong services are reachable over a network. The provided sources do not identify affected deployment modes beyond Apache InLong itself.
Exploitation context
The CVE has a 9.8 CVSS v3.1 score with AV:N/AC:L/PR:N/UI:N. The bundle does not show CISA KEV listing or cite active exploitation, so active exploitation should not be claimed from this evidence.
Researcher notes
Evidence is strong for product, affected range, weakness class, CVSS vector, and vendor remediation direction. Public source evidence provided here does not include exploit availability, affected configurations, or proof of active exploitation.
Mitigation direction
- Upgrade Apache InLong to the latest version recommended by Apache.
- If upgrading is blocked, evaluate cherry-picking Apache PR 7223.
- Prioritize remediation for InLong 1.1.0 through 1.5.0 deployments.
- Monitor Apache advisory and CVE updates for changed guidance.
Validation and detection
- Inventory Apache InLong deployments and record exact versions.
- Confirm no production system runs InLong 1.1.0 through 1.5.0.
- Verify upgraded builds include the vendor fix or PR 7223.
- Review SBOMs and deployment manifests for embedded InLong components.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-24997 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://lists.apache.org/thread/nxvtxq7oxhwyzo9ty2hqz8rvh5r7ngd8CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.