LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40583: Pentaminds CuroVMS v2.0.1 was discovered to contain exposed credentials.

Pentaminds CuroVMS v2.0.1 was discovered to contain exposed credentials.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-40583 reports exposed credentials in Pentaminds CuroVMS v2.0.1. If an organization runs this version, unauthorized parties may be able to obtain sensitive access material. The CVSS score is 9.1, driven by network reachability, no required login, and high confidentiality and availability impact.

Executive priority

Prioritize inventory and containment if CuroVMS v2.0.1 is used. The issue concerns exposed credentials and carries a critical CVSS rating, but public sources in the bundle do not provide a confirmed patch or active exploitation evidence.

Technical view

The record describes CWE-522, insufficiently protected credentials, in Pentaminds CuroVMS v2.0.1. CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. The public record provides limited product metadata and no vendor remediation detail in the supplied sources.

Likely exposure

Most relevant to organizations using Pentaminds CuroVMS v2.0.1, especially if reachable from untrusted networks. The source bundle does not identify CPEs, deployment patterns, default exposure, or affected versions beyond v2.0.1.

Exploitation context

The CVE is not listed as CISA KEV in the supplied data. A public researcher write-up exists, but the provided sources do not prove active exploitation in the wild. Treat public disclosure as increasing discovery and scanning risk.

Researcher notes

Evidence is sparse: the CVE description is brief, affected CPE data is absent, and remediation details are not included. Analysis should stay anchored to v2.0.1 unless additional vendor or CNA information confirms broader impact.

Mitigation direction

  • Identify whether Pentaminds CuroVMS v2.0.1 is deployed.
  • Check Pentaminds or product maintainer guidance for updates or configuration changes.
  • Restrict network access to CuroVMS interfaces where business requirements allow.
  • Rotate any credentials that may be stored or exposed by the application.
  • Review logs for suspicious access to credential-bearing pages, files, or APIs.

Validation and detection

  • Confirm installed CuroVMS version from asset inventory or application administration records.
  • Check whether the service is reachable from the internet or untrusted networks.
  • Review the CVE and researcher reference for affected-version confirmation.
  • Verify credentials associated with CuroVMS have been rotated after remediation decisions.
  • Document compensating controls if vendor guidance is unavailable.
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-522: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-40583 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
Critical
CVSS
9.1 (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: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
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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2024-40583Attack 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:H

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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-522 · source CWE mapping

Insufficiently Protected Credentials

Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.