Yes. com.liferay:com.liferay.login.authentication.openid.connect.web (Maven): upgrade to 1.0.1 or later; com.liferay:com.liferay.login.web (Maven): upgrade to 1.1.20 or later; com.liferay.portal:release.portal.bom (Maven): upgrade to 7.0.3-GA4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-12646?
Check whether you run com.liferay:com.liferay.login.authentication.openid.connect.web (Maven), com.liferay:com.liferay.login.web (Maven) or com.liferay.portal:release.portal.bom (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
com.liferay:com.liferay.login.authentication.openid.connect.web (Maven): upgrade to 1.0.1 or later
# set com.liferay:com.liferay.login.authentication.openid.connect.web to 1.0.1 in your pom.xml or build.gradle
com.liferay:com.liferay.login.web (Maven): upgrade to 1.1.20 or later
# set com.liferay:com.liferay.login.web to 1.1.20 in your pom.xml or build.gradle
com.liferay.portal:release.portal.bom (Maven): upgrade to 7.0.3-GA4 or later
# set com.liferay.portal:release.portal.bom to 7.0.3-GA4 in your pom.xml or build.gradle