dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-62691

CRITICAL · 9.8 CVSS v3.0 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Security Point (Windows) of MaLion and MaLionCloud contains a stack-based buffer overflow vulnerability in processing HTTP headers. Receiving a specially crafted request from a remote unauthenticated attacker could lead to arbitrary code execution with SYSTEM privilege.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow vulnerability in MaLion and MaLionCloud Windows security products when processing HTTP headers. Remote unauthenticated attackers can send specially crafted HTTP requests to achieve arbitrary code execution with SYSTEM privileges.

MitigationApply vendor-supplied patch immediately. If unavailable, implement network segmentation to restrict access to the affected service and deploy WAF/IPS rules to detect and block malformed HTTP header payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if MaLion or MaLionCloud is installed
    Check the Windows program list: Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell to list installed software. Look for entries containing 'MaLion' or 'MaLionCloud'.
    Affected if No MaLion or MaLionCloud entry is found in installed programs.
  2. Determine installed version of MaLion/MaLionCloud
    Once installed product is confirmed, note the version shown in Programs and Features, or right-click the application in the Start menu and select 'Properties' to view the File Version. Record this version number for comparison against vendor advisories.
    Affected if The installed version is unknown or cannot be determined.
  3. Check if HTTP management interface is enabled
    MaLion products expose an HTTP service for management. Check for listening ports (typically 8443, 9443, or similar) by running 'netstat -ano | findstr LISTENING' or using PowerShell 'Get-NetTCPConnection -State Listen'. Look for services bound to these ports associated with MaLion processes.
    Affected if HTTP management ports are open and listening, indicating the affected service is exposed.
  4. Identify MaLion HTTP service process
    Use Task Manager or run 'tasklist /FI "IMAGENAME eq *.exe" /V' to find MaLion-related processes. Identify the main executable handling HTTP requests (often named similarly to the product). Note the process ID and running user context.
    Affected if Process is running as SYSTEM or with elevated privileges, making exploitation high-impact.
  5. Inspect HTTP service configuration files
    Locate MaLion configuration files in the installation directory (commonly C:\Program Files\MaLion\ or C:\Program Files (x86)\MaLion\). Check config files for HTTP listener settings, port bindings, and enablement status. Look for XML or INI files containing 'HTTP', 'Port', 'Listener', or 'WebServer' keywords.
    Affected if HTTP service is explicitly enabled in configuration files.

A system is affected if MaLion or MaLionCloud is installed with the HTTP management interface enabled, and the installed version falls within the vulnerable version range per vendor documentation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch immediately. If unavailable, implement network segmentation to restrict access to the affected service and deploy WAF/IPS rules to detect and block malformed HTTP header payloads.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62691 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data