In 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 bef
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.4.3.26-ga26, 7.2.10.fp19, 7.3.10.u5, 7.4.13.u26
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Liferay Portal
From 7.2.0 · through 7.4.3.25
- Liferay DXP
From 7.4.13 · through 7.4.13.u25; From 7.3.10 · through 7.3.10.u4; From 7.2.10 · through 7.2.10-dxp-18
- com.liferay.portal:release.portal.bomMaven
From 7.2.0 · fixed in 7.4.3.26-ga26
- com.liferay.portal:release.dxp.bomMaven
fixed in 7.2.10.fp19
- com.liferay.portal:release.dxp.bomMaven
From 7.3.0 · fixed in 7.3.10.u5
- com.liferay.portal:release.dxp.bomMaven
From 7.4.0 · fixed in 7.4.13.u26