Liferay Portal and Liferay DXP HTTP Header Can Expose Versions
Liferay Portal · Liferay DXP
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| com.liferay.portal:release.portal.bom Maven |
|
|
| com.liferay.portal:release.dxp.bom Maven |
|
Liferay Portal · Liferay DXP
| Product | Affected | Fixed in |
|---|---|---|
| com.liferay.portal:release.portal.bom Maven |
|
|
| com.liferay.portal:release.dxp.bom Maven |
|
7.2.10.fp197.3.10.u57.4.13.u26In Liferay Portal 7.2.0 through 7.4.3.25, and older unsupported versions, and Liferay DXP 7.4 before update 26, 7.3 before update 5, 7.2 before fix pack 19, and older unsupported versions the default value of the portal property `http.header.version.verbosity` is set to `full`, which allows remote attackers to easily identify the version of the application that is running and the vulnerabilities that affect that version via 'Liferay-Portal` response header.
From the CVE record · Liferay
The default `http.header.version.verbosity` setting is `full`, exposing the running application version in the `Liferay-Portal` response header. Remote attackers can use that header to identify the version and vulnerabilities affecting it.
Teams running Liferay Portal 7.2.0 through 7.4.3.25 or Liferay DXP 7.4 before update 26, 7.3 before update 5, or 7.2 before fix pack 19 should check their installations; older unsupported versions are also affected.