LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40582: Pentaminds CuroVMS v2.0.1 was discovered to contain exposed sensitive information.

Pentaminds CuroVMS v2.0.1 was discovered to contain exposed sensitive information.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-40582 is a high-severity information exposure issue reported in Pentaminds CuroVMS v2.0.1. An unauthenticated network attacker may be able to access sensitive information. The main business risk is confidentiality loss, not system takeover or outage based on the published CVSS vector.

Executive priority

Prioritize review within the next remediation cycle, faster for internet-facing systems or environments handling confidential video, credentials, or personal data. The issue threatens data confidentiality and may trigger incident response if exposure is confirmed.

Technical view

The CVE describes exposed sensitive information in Pentaminds CuroVMS v2.0.1, mapped to CWE-312. CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, indicating remotely reachable, low-complexity, unauthenticated confidentiality impact only. The record does not name a fixed version.

Likely exposure

Organizations running Pentaminds CuroVMS v2.0.1 are the known exposed population. The source bundle’s structured affected-product data is incomplete, so verify product identity and version directly in asset inventories.

Exploitation context

A public researcher write-up is referenced, but the source bundle does not establish active exploitation. CISA KEV status is false. Treat internet-facing CuroVMS deployments as higher priority because the CVSS vector indicates network access without authentication.

Researcher notes

Evidence is sparse: the CVE description is brief, affected metadata is not normalized, and no patch is named. Avoid assuming broader versions or products. Focus validation on confirming v2.0.1 exposure, reachable attack surface, and whether sensitive data can be accessed improperly.

Mitigation direction

  • Identify whether Pentaminds CuroVMS v2.0.1 is deployed.
  • Check Pentaminds or product maintainer guidance for updates or configuration fixes.
  • Restrict CuroVMS access to trusted networks or VPN where operationally possible.
  • Review exposed files, logs, backups, and configuration areas for sensitive data.
  • Rotate credentials if sensitive secrets may have been exposed.

Validation and detection

  • Confirm CuroVMS version and deployment locations from inventory.
  • Determine whether any CuroVMS instance is internet-accessible.
  • Review application and web server logs for unusual access to sensitive resources.
  • Assess whether sensitive data is stored or exposed without adequate protection.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

Public sources used

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-312: 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-2024-40582 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:H/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

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:H/I:N/A:N3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-312

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