Apache Inlong
Monthly
Argument injection in Apache InLong's Agent Installer (versions 2.0.0 through 2.3.x) enables arbitrary shell command execution via the ModuleManager's ExcuteLinux.exeCmd() method, which applies no input filtering or whitelist validation. Any deployment running InLong agents within the affected version range is exposed to OS-level command execution on the agent host system. Apache has released version 2.4.0 as the authoritative fix; no public exploit has been identified at time of analysis.
Server-Side Request Forgery in Apache InLong Manager (versions 2.0.0-2.3.x) allows any authenticated user - no administrative role required - to coerce the Manager service into issuing outbound HTTP requests or TCP connections to arbitrary internal hosts and ports. This effectively turns the InLong Manager into an open proxy for internal network reconnaissance, enabling access to otherwise firewalled services such as cloud instance metadata endpoints, internal APIs, or database management interfaces. No public exploit has been identified at time of analysis, but the low privilege bar makes this broadly reachable within any deployment that permits shared user access.
Arbitrary file read in Apache InLong 2.0.0 through 2.3.x exposes the Agent host filesystem to unauthenticated remote attackers via a relative path traversal flaw. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms exploitation requires no credentials or user interaction, making any network-exposed InLong Agent endpoint a direct confidentiality risk. No public exploit code and no CISA KEV listing have been identified at time of analysis; EPSS sits at 0.21% (12th percentile), indicating low observed exploitation probability despite the high base score.
Broken access control in Apache InLong's manager component exposes Data Node management endpoints to any authenticated user, regardless of their assigned role or privilege level. Versions 2.0.0 through 2.3.x are affected, allowing any valid manager account holder to create, modify, or delete Data Node definitions that underpin the platform's data pipeline infrastructure. The CVSS 8.1 High rating reflects high integrity and availability impact; no public exploit or CISA KEV listing exists at time of analysis.
Missing authorization enforcement in Apache InLong's StreamSource component allows any authenticated user - regardless of role - to logically delete all stream sources across the platform. Versions 2.0.0 through 2.3.x are affected; the root cause is CWE-552, where the StreamSource API performs no access-control check before executing the delete operation. No public exploit code is currently known and the vulnerability is absent from CISA KEV, but the extremely low exploitation barrier - a single valid account - makes this a serious risk for any multi-tenant or shared InLong deployment.
SQL injection in Apache InLong versions 2.0.0 up to (but not including) 2.4.0 allows attackers to inject attacker-controlled string values into a SQL statement, giving full read/write access to the backing database. The flaw carries a critical CVSS 3.1 score of 9.8 (network, no authentication, no user interaction) and is fixed in 2.4.0. No public exploit identified at time of analysis, and the EPSS probability is low (0.19%, 9th percentile), so despite the critical score there is no evidence of active exploitation yet.
SQL injection in Apache InLong versions 2.0.0 through 2.3.x allows remote attackers to inject arbitrary SQL via the dbName, tableName, schemaName, and username parameters, compromising the integrity and confidentiality of the backend database. The flaw carries a CVSS 9.8 (network, no authentication, no user interaction) and was disclosed by the Apache project itself; a vendor patch exists in 2.4.0. There is no public exploit identified at time of analysis, and EPSS estimates exploitation probability at a low 0.21% (11th percentile).
Uncontrolled Resource Consumption (CWE-400) in Apache InLong versions 2.0.0 through 2.3.x exposes two related attack surfaces: authenticated users can trigger excessive resource consumption to degrade service availability, and the same pathway permits upload of non-official packages, introducing a package-integrity risk alongside the denial-of-service vector. Affected deployments running any release in the 2.0.0-2.3.x range should treat this as a priority upgrade given the dual nature of the flaw. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Unauthorized template information disclosure in Apache InLong 2.0.0 through 2.3.x allows authenticated users who are not designated template responsible persons to view template configurations they should not have access to. The CVE is tagged CWE-400 (Uncontrolled Resource Consumption) and classified as Denial of Service, yet the description describes an access control bypass - this is a data contradiction that analysts should flag before making control decisions. No public exploit or active exploitation has been identified. Vendor fix is available in Apache InLong 2.4.0.
Argument injection in Apache InLong's Agent Installer (versions 2.0.0 through 2.3.x) enables arbitrary shell command execution via the ModuleManager's ExcuteLinux.exeCmd() method, which applies no input filtering or whitelist validation. Any deployment running InLong agents within the affected version range is exposed to OS-level command execution on the agent host system. Apache has released version 2.4.0 as the authoritative fix; no public exploit has been identified at time of analysis.
Server-Side Request Forgery in Apache InLong Manager (versions 2.0.0-2.3.x) allows any authenticated user - no administrative role required - to coerce the Manager service into issuing outbound HTTP requests or TCP connections to arbitrary internal hosts and ports. This effectively turns the InLong Manager into an open proxy for internal network reconnaissance, enabling access to otherwise firewalled services such as cloud instance metadata endpoints, internal APIs, or database management interfaces. No public exploit has been identified at time of analysis, but the low privilege bar makes this broadly reachable within any deployment that permits shared user access.
Arbitrary file read in Apache InLong 2.0.0 through 2.3.x exposes the Agent host filesystem to unauthenticated remote attackers via a relative path traversal flaw. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms exploitation requires no credentials or user interaction, making any network-exposed InLong Agent endpoint a direct confidentiality risk. No public exploit code and no CISA KEV listing have been identified at time of analysis; EPSS sits at 0.21% (12th percentile), indicating low observed exploitation probability despite the high base score.
Broken access control in Apache InLong's manager component exposes Data Node management endpoints to any authenticated user, regardless of their assigned role or privilege level. Versions 2.0.0 through 2.3.x are affected, allowing any valid manager account holder to create, modify, or delete Data Node definitions that underpin the platform's data pipeline infrastructure. The CVSS 8.1 High rating reflects high integrity and availability impact; no public exploit or CISA KEV listing exists at time of analysis.
Missing authorization enforcement in Apache InLong's StreamSource component allows any authenticated user - regardless of role - to logically delete all stream sources across the platform. Versions 2.0.0 through 2.3.x are affected; the root cause is CWE-552, where the StreamSource API performs no access-control check before executing the delete operation. No public exploit code is currently known and the vulnerability is absent from CISA KEV, but the extremely low exploitation barrier - a single valid account - makes this a serious risk for any multi-tenant or shared InLong deployment.
SQL injection in Apache InLong versions 2.0.0 up to (but not including) 2.4.0 allows attackers to inject attacker-controlled string values into a SQL statement, giving full read/write access to the backing database. The flaw carries a critical CVSS 3.1 score of 9.8 (network, no authentication, no user interaction) and is fixed in 2.4.0. No public exploit identified at time of analysis, and the EPSS probability is low (0.19%, 9th percentile), so despite the critical score there is no evidence of active exploitation yet.
SQL injection in Apache InLong versions 2.0.0 through 2.3.x allows remote attackers to inject arbitrary SQL via the dbName, tableName, schemaName, and username parameters, compromising the integrity and confidentiality of the backend database. The flaw carries a CVSS 9.8 (network, no authentication, no user interaction) and was disclosed by the Apache project itself; a vendor patch exists in 2.4.0. There is no public exploit identified at time of analysis, and EPSS estimates exploitation probability at a low 0.21% (11th percentile).
Uncontrolled Resource Consumption (CWE-400) in Apache InLong versions 2.0.0 through 2.3.x exposes two related attack surfaces: authenticated users can trigger excessive resource consumption to degrade service availability, and the same pathway permits upload of non-official packages, introducing a package-integrity risk alongside the denial-of-service vector. Affected deployments running any release in the 2.0.0-2.3.x range should treat this as a priority upgrade given the dual nature of the flaw. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Unauthorized template information disclosure in Apache InLong 2.0.0 through 2.3.x allows authenticated users who are not designated template responsible persons to view template configurations they should not have access to. The CVE is tagged CWE-400 (Uncontrolled Resource Consumption) and classified as Denial of Service, yet the description describes an access control bypass - this is a data contradiction that analysts should flag before making control decisions. No public exploit or active exploitation has been identified. Vendor fix is available in Apache InLong 2.4.0.