7 matches found
CVE-2020-24030
CVE-2020-24030 説明 ForLogic Qualiex v1 および v3 には、トークンの有効期限が弱いという問題があります。これにより、リモートの未認証ユーザーがトークンを再利用して権限を昇格させ、機密データにアクセスできる可能性があります。 重要日付 ベンダーへの通知: 2020-07-12 公開日: 2020-08-31 脆弱性タイプ 不適切なアクセス制御 製品ベンダー ForLogic 影響を受ける製品コードベース Qualiex - v1 Qualiex - v3 他のバージョンも影響を受ける可能性があります。特に同じファミリーのバージョン(未テスト)...
CVE-2020-24030
ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is "not exploitable in the current implementation. Tokens are properly expire...
CVE-2020-24030
ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is "not exploitable in the current implementation. Tokens are properly expire...
Privilege escalation
ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse...
CVE-2020-24030
ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is "not exploitable in the current implementation. Tokens are properly expire...
CVE-2020-24030
CVE-2020-24030 affects ForLogic Qualiex v1 and v3, where weak token expiration allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. Across connected sources, the issue is tied to token handling rather than a traditional flaw in application logic. The Re...
CVE-2020-24030: Operation on a Resource after Expiration or Release
ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is "not exploitable in the current implementation. Tokens are properly expire...