Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2010-1428 CISA KEV high CVSS 7.5

[KEV] Vulnerability in Red Hat JBoss (CVE-2010-1428)

Summary

Vulnerability in Red Hat JBoss (CVE-2010-1428). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited.

Original description

The description as published by the source.

Unauthenticated access to the JBoss Application Server Web Console (/web-console) is blocked by default. However, it was found that this block was incomplete, and only blocked GET and POST HTTP verbs. A remote attacker could use this flaw to gain access to sensitive information.

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-2010-1428 has been found in Red Hat JBoss.
Confidential information can be exposed externally. CVSS score: 7.5/10.
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 "Red Hat JBoss CVE-2010-1428" on the vendor's site.

CVE-2010-1428 (Red Hat JBoss) — CWE-749 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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

A vulnerability (CWE-749) exists in Red Hat JBoss.

📍 Affected scope

Check the vendor advisory for the affected versions of Red Hat JBoss.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally. 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・依存マニフェストで Red Hat JBoss を使っているサービスとバージョンを洗い出す。

  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