Categories
CVE-2025-13948 medium CVSS 5.6

Vulnerability in opsre go-ldap-admin (CVE-2025-13948)

Summary

Vulnerability in opsre go-ldap-admin (CVE-2025-13948). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

A vulnerability was determined in opsre go-ldap-admin up to 20251011. This issue affects some unknown processing of the file docs/docker-compose/docker-compose.yaml of the component JWT Handler. Executing manipulation of the argument secret key can lead to use of hard-coded cryptographic key . The attack can be launched remotely. Attacks of this nature are highly complex. The exploitability is assessed as difficult. The exploit has been publicly disclosed and may be utilized.

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-13948 has been found in opsre go-ldap-admin.
Risk of unauthorized operations or information disclosure. CVSS score: 5.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "opsre go-ldap-admin CVE-2025-13948" on the vendor's site.

CVE-2025-13948 (opsre go-ldap-admin) — CWE-320 / CVSS v3 5.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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-320) exists in opsre go-ldap-admin.

📍 Affected scope

Check the vendor advisory for the affected versions of opsre go-ldap-admin.

🔥 Severity

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

🔧 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・依存マニフェストで opsre go-ldap-admin を使っているサービスとバージョンを洗い出す。

  2. 2
    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