Vulnerability in Liferay Portal (CVE-2023-33949)

Summary

Vulnerability in Liferay Portal (CVE-2023-33949). Data can be tampered with by attackers. Exploitable via company.security.strangers.verify.

Original description

The description as published by the source.

In Liferay Portal 7.3.0 and earlier, and Liferay DXP 7.2 and earlier the default configuration does not require users to verify their email address, which allows remote attackers to create accounts using fake email addresses or email addresses which they don't control. The portal property company.security.strangers.verify should be set to true.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-33949 has been found in Liferay Portal.
Attackers can target a specific entry point like company.security.strangers.verify over the network to misuse the product.
Data can be tampered with by attackers.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Liferay Portal CVE-2023-33949" on the vendor's site.

CVE-2023-33949 (Liferay Portal)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: company.security.strangers.verify
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Liferay Portal. Attackers reach the vulnerable code path via company.security.strangers.verify without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Liferay Portal. Attack surface: company.security.strangers.verify.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Liferay Portal を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

advisory liferay.dev