LiveActive security incident?Get immediate response
CVE Record

CVE-2019-5645: Rapid7 Metasploit HTTP Handler Denial of Service

By sending a specially crafted HTTP GET request to a listening Rapid7 Metasploit HTTP handler, an attacker can register an arbitrary regular expression. When evaluated, this malicious handler can either prevent new HTTP handler sessions from being established, or cause a resource exhaustion on the Metasploit server.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue lets an unauthenticated network attacker disrupt a Rapid7 Metasploit Framework HTTP handler. Successful abuse can stop new handler sessions or exhaust server resources. The impact is availability loss, not data theft or code execution, based on the provided sources.

Executive priority

Treat as high priority where Metasploit handlers are reachable from untrusted networks. The business risk is disruption of security testing infrastructure and possible interruption of authorized operations. If handlers are isolated and access-controlled, schedule remediation through normal urgent maintenance.

Technical view

CVE-2019-5645 affects Rapid7 Metasploit Framework 5.0.27. A crafted HTTP GET request to a listening Metasploit HTTP handler can register an arbitrary regular expression that disrupts handler session creation or causes resource exhaustion. The CVSS 3.1 score is 7.5, network-accessible, low complexity, no privileges, no user interaction.

Likely exposure

Exposure is limited to environments running Rapid7 Metasploit Framework 5.0.27 with HTTP handlers listening where an attacker can reach them. Internet-reachable or broadly accessible internal handler listeners are the main concern. The source bundle does not identify other affected versions or CPEs.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The weakness is remotely reachable when an HTTP handler is listening, but the public evidence here supports denial of service only.

Researcher notes

Evidence is concise and limited. The provided CVE data names Rapid7 Metasploit Framework 5.0.27, CWE-400, and a Rapid7 pull request. It does not provide a fixed version, CPE list, workaround text, or active exploitation evidence.

Mitigation direction

  • Inventory Metasploit Framework deployments and identify version 5.0.27.
  • Restrict network access to Metasploit HTTP handlers to trusted operators only.
  • Check Rapid7 guidance or the referenced pull request for fixed version details.
  • Upgrade or patch according to Rapid7’s documented remediation path.
  • Monitor Metasploit hosts for handler failures or resource exhaustion.

Validation and detection

  • Confirm whether any Metasploit Framework 5.0.27 instances are present.
  • Review firewall and access-control rules around HTTP handler listener ports.
  • Check operational logs for unexpected handler errors or resource exhaustion symptoms.
  • Verify patched or upgraded instances remain functional for authorized testing workflows.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-5645 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2019-5645Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Rapid7Metasploit Framework5.0.27Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.