# CVE-2025-34143: ETQ Reliance CG Authentication Bypass via Trailing Space RCE

- Exploited (CISA KEV): no
- Published: 2025-07-22
- CVSS: 9.3 CRITICAL (v4.0)
- EPSS: 38.0% (99th percentile)
- CWE: CWE-288, CWE-269, CWE-78

An authentication bypass vulnerability exists in ETQ Reliance on the CG (legacy) platform. The application allowed login as the privileged internal SYSTEM user by manipulating the username field. The SYSTEM account does not require a password, enabling attackers with network access to the login page to obtain elevated access. Once authenticated, an attacker could achieve remote code execution by modifying Jython scripts within the application. This issue was resolved by introducing stricter validation logic to exclude internal accounts from public authentication workflows in version MP-4583.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | No public claim | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | No public claim | — | — |
| Fastly | Before feed history | — | — |
| F5 | Rule published | 2025-12-03 | 134 |
| Akamai | No public source | — | — |
| OWASP CRS | No public claim | — | — |

### F5

- 2025-12-03 · new · rule 200013132
  > Added: signature 200013132 "ETQ Reliance Authentication Bypass" (Authentication/Authorization Attacks, risk High), systems: Java Servlets/JSP, Other Web Server, JavaServer Faces (JSF). References: CVE-2025-34143.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog

## Our test (measured)

- OWASP Core Rule Set 4.25.0, paranoia level 1, anomaly threshold 5, default CRS settings: passed (0 of 1 requests blocked), template CVE-2025-34143, 2026-11-02
- OWASP Core Rule Set 4.25.0, paranoia level 2, anomaly threshold 5, default CRS settings: passed (0 of 1 requests blocked), template CVE-2025-34143, 2026-11-02

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2025-34143 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2025-34143