CVE-2025-34140

An authorization bypass vulnerability exists in ETQ Reliance (legacy CG and NXG SaaS platforms). By appending a specific URI suffix to certain API endpoints, an unauthenticated attacker can bypass access control checks and retrieve limited sensitive resources. The root cause was a misconfiguration in API authorization logic, which has since been corrected in SE.2025.1 and 2025.1.2.

CVSS

No CVSS.

References

Link	Resource
https://www.etq.com/blog/etq-reliance-security-update/
https://www.etq.com/product-overview/

Configurations

No configuration.

History

25 Jul 2025, 15:29

Type	Values Removed	Values Added
Summary		(es) Existe una vulnerabilidad de omisión de autorización en ETQ Reliance (plataformas SaaS CG y NXG legacy). Al añadir un sufijo URI específico a ciertos endpoints de API, un atacante no autenticado puede eludir las comprobaciones de control de acceso y recuperar recursos confidenciales limitados. La causa principal fue una configuración incorrecta en la lógica de autorización de la API, que ya se ha corregido en SE.2025.1 y 2025.1.2.

22 Jul 2025, 13:15

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-07-22 13:15

Updated : 2025-07-25 15:29

NVD link : CVE-2025-34140

Mitre link : CVE-2025-34140

CVE.ORG link : CVE-2025-34140

JSON object : View

Products Affected

No product.

CWE

CWE-639

Authorization Bypass Through User-Controlled Key

{"id": "CVE-2025-34140", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "disclosure@vulncheck.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.7, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-07-22T13:15:23.957", "references": [{"url": "https://www.etq.com/blog/etq-reliance-security-update/", "source": "disclosure@vulncheck.com"}, {"url": "https://www.etq.com/product-overview/", "source": "disclosure@vulncheck.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "disclosure@vulncheck.com", "description": [{"lang": "en", "value": "CWE-639"}]}], "descriptions": [{"lang": "en", "value": "An authorization bypass vulnerability exists in ETQ Reliance (legacy CG and NXG SaaS platforms). By appending a specific URI suffix to certain API endpoints, an unauthenticated attacker can bypass access control checks and retrieve limited sensitive resources. The root cause was a misconfiguration in API authorization logic, which has since been corrected in SE.2025.1 and 2025.1.2."}, {"lang": "es", "value": "Existe una vulnerabilidad de omisi\u00f3n de autorizaci\u00f3n en ETQ Reliance (plataformas SaaS CG y NXG legacy). Al a\u00f1adir un sufijo URI espec\u00edfico a ciertos endpoints de API, un atacante no autenticado puede eludir las comprobaciones de control de acceso y recuperar recursos confidenciales limitados. La causa principal fue una configuraci\u00f3n incorrecta en la l\u00f3gica de autorizaci\u00f3n de la API, que ya se ha corregido en SE.2025.1 y 2025.1.2."}], "lastModified": "2025-07-25T15:29:44.523", "sourceIdentifier": "disclosure@vulncheck.com"}