Categories
CVE-2023-46748 CISA KEV high

[KEV] SQL Injection in F5 BIG-IP Configuration Utility (CVE-2023-46748)

Summary

SQL injection in F5 BIG-IP Configuration Utility (CVE-2023-46748). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited.

Original description

The description as published by the source.

F5 BIG-IP Configuration utility contains an SQL injection vulnerability that may allow an authenticated attacker with network access through the BIG-IP management port and/or self IP addresses to execute system commands. This vulnerability can be used in conjunction with CVE-2023-46747.

Source: CISA Known Exploited Vulnerabilities NVD CISA KEV

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-46748 has been found in F5 BIG-IP Configuration Utility.
Risk of unauthorized operations or information disclosure.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "F5 BIG-IP Configuration Utility CVE-2023-46748" on the vendor's site.

CVE-2023-46748 (F5 BIG-IP Configuration Utility) — CWE-89
Listed in CISA KEV — actively exploited, treat as top priority.
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

SQL injection (CWE-89) exists in F5 BIG-IP Configuration Utility.

📍 Affected scope

Check the vendor advisory for the affected versions of F5 BIG-IP Configuration Utility.

🔥 Severity

Severity: High. Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 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. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで F5 BIG-IP Configuration Utility を使っているサービスとバージョンを洗い出す。

  2. 2
    Consider incident declaration escalate
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details