Apache NiFi: Improper Escaping of Table Names in CaptureChangeMySQL
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache NiFi | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Apache | Nifi |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-chxj-gxww-q98w | Apache NiFi: Improper Escaping of Table Names in CaptureChangeMySQL |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.646% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache nifi |
|
| Vendors & Products |
Apache
Apache nifi |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper escaping of database table names in the CaptureChangeMySQL Processor included with Apache NiFi 1.2.0 through 2.9.0 allows for injecting SQL commands using crafted naming. Manual quoted boundaries added in Apache NiFi 1.8.0 narrowed the scope of potential injection options, but did not cover additional strategies. Apache NiFi installations that do not use the CaptureChangeMySQL Processor are not subject to this vulnerability. Upgrading to Apache NiFi 2.10.0 is the recommended mitigation, which incorporates more robust identifier escaping. | |
| Title | Apache NiFi: Improper Escaping of Table Names in CaptureChangeMySQL | |
| Weaknesses | CWE-116 | |
| References |
| |
| Metrics |
cvssV4_0
|