6.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-27522

CVE-2025-27522: Apache InLong: JDBC Vulnerability during verification processing

Deserialization of Untrusted Data vulnerability in Apache InLong.

This issue affects Apache InLong: from 1.13.0 through 2.1.0. This vulnerability is a secondary mining bypass for CVE-2024-26579. Users are advised to upgrade to Apache InLong's 2.2.0 or cherry-pick [1] to solve it.

[1]

https://github.com/apache/inlong/pull/11732

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-27522

CVE-2025-27522:

6.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
org.apache.inlong:manager-pojo	maven	>= 1.13.0, < 2.2.0	2.2.0

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the case-sensitive checking of sensitive parameters within JDBC URLs, specifically in the MySQLSensitiveUrlUtils.containSensitiveKey method. Parameters like autoDeserialize, allowLoadLocalInfile, and allowUrlInLocalInfile are intended to be disabled or handled carefully. The original code checked for these parameters using exact string matches (e.g., key + "=true"). An attacker could bypass this check by using mixed casing (e.g., autoDeserialize=TRue). This bypass would mean that the MySQLSensitiveUrlUtils.filterSensitive method, which relies on containSensitiveKey, would fail to remove or neutralize these dangerous parameters. Consequently, higher-level functions like MySQLSinkDTO.filterSensitive that use these utilities would operate on unsanitized JDBC URLs. If such a URL with a parameter like autoDeserialize=TRue (bypassing the filter) is used to establish a JDBC connection, it could lead to deserialization of untrusted data, as indicated by the CVE description (CWE-502). The patch addresses this by changing the checks in containSensitiveKey to be case-insensitive using StringUtils.containsIgnoreCase.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.