Missing Authentication Vulnerability in JTL-WMS
What fixes it
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
The authorization middleware of the WMS MobileServer fails to require authentication in two distinct cases. First, it only requires an Authorization header for GET and HEAD requests; requests using any other HTTP method are processed without an authentication check. Second, for any HTTP method including GET and HEAD, a request carrying a malformed or non-bearer Authorization header is passed through without a valid token being required.
The middleware does validate a token whenever a well-formed one is present, but in these two cases it does not require one. A remote attacker with network access to the service can therefore invoke API functionality without valid credentials.
Text from CVE List
Affected versions 4
- JTL-WMSaffected: all versions before 2.0.7CVE List
- JTL-WMSaffected: all versions before 2.1.2CVE List
- JTL-WMSaffected: all versions before 2.2.1CVE List
- JTL-WMSaffected: 1.7.*, 1.8.*, 1.9.*, 1.10.*, 1.11.*CVE List