LiveActive security incident?Get immediate response
CVE Record

CVE-2019-5642: MAGICK

Rapid7 Metasploit Pro version 4.16.0-2019081901 and prior suffers from an instance of CWE-732, wherein the unique server.key is written to the file system during installation with world-readable permissions. This can allow other users of the same system where Metasploit Pro is installed to intercept otherwise private communications to the Metasploit Pro web interface.

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This issue exposed Metasploit Pro’s unique server key with overly broad file permissions during installation. A local user on the same host could read it and potentially intercept private communications to the Metasploit Pro web interface. The business risk is limited but relevant on shared or poorly controlled systems.

Executive priority

Handle during normal vulnerability remediation, with faster action for shared administration hosts or systems with broad local access. This is not internet-remote code execution, but it can undermine trust in management interface confidentiality.

Technical view

CVE-2019-5642 is a CWE-732 permissions flaw in Rapid7 Metasploit Pro 4.16.0-2019081901 and prior. The installer writes the unique server.key to disk as world-readable. The CVSS 3.1 score is 3.3, requiring local access and low privileges, with confidentiality impact only.

Likely exposure

Exposure is most likely where Metasploit Pro was installed on multi-user systems, jump boxes, shared administration hosts, or servers with unnecessary local accounts. Single-user, tightly administered hosts have lower practical exposure.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Abuse requires local access to the host and a readable server.key, then could compromise confidentiality of web interface communications.

Researcher notes

The core issue is excessive permissions on a unique private key file. The source bundle provides affected version bounds and impact, but does not include detailed exploit evidence, exact fixed version semantics beyond the Rapid7 release-note reference, or key rotation instructions.

Mitigation direction

  • Review Rapid7 guidance and release notes for the referenced Metasploit Pro update.
  • Upgrade affected Metasploit Pro installations if Rapid7 identifies the release as fixed.
  • Restrict local account access to systems running Metasploit Pro.
  • Remove world-readable access from sensitive key files according to vendor guidance.
  • Treat exposed keys as potentially compromised and follow Rapid7 rotation guidance if available.

Validation and detection

  • Inventory Metasploit Pro installations and identify versions 4.16.0-2019081901 and prior.
  • Check whether server.key exists with world-readable permissions on installed systems.
  • Review local user accounts on affected hosts for unnecessary access.
  • Confirm the Rapid7-referenced update or later vendor-approved remediation is applied.
  • Look for internal evidence that unauthorized local users accessed the key file.
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 · medium confidence lookup

CWE-732: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-5642 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
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

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

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
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2019-5642Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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 ProunspecifiedListed
Weakness

CWE details

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

CWE-732 · source CWE mapping

Incorrect Permission Assignment for Critical Resource

Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.