Categories
CVE-2025-66433 medium CVSS 4.2

Authorization Flaw in HTCondor Access Point (CVE-2025-66433)

Summary

Vulnerability in HTCondor Access Point (CVE-2025-66433). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 24.12.14 or later.

Original description

The description as published by the source.

HTCondor Access Point before 25.3.1 allows an authenticated user to impersonate other users on the local machine by submitting a batch job. This is fixed in 24.12.14, 25.0.3, and 25.3.1. The earliest affected version is 24.7.3.

Source: NIST National Vulnerability Database NVD

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-2025-66433 has been found in HTCondor Access Point.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade HTCondor Access Point to 24.12.14 or later.
If unsure, ask your IT team or search "HTCondor Access Point CVE-2025-66433" on the vendor's site.

CVE-2025-66433 (HTCondor Access Point) — CWE-863 / CVSS v3 4.2
Attack vector: local / no user interaction
Patched: 24.12.14 — apply immediately
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

Incorrect authorization (CWE-863) exists in HTCondor Access Point.

📍 Affected scope

Check the vendor advisory for the affected versions of HTCondor Access Point.

🔥 Severity

Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 24.12.14.

🛡️ 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・依存マニフェストで HTCondor Access Point を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade HTCondor Access Point to 24.12.14

    ステージング環境で 24.12.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  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