LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41542: devhub 0.102.0 was discovered to contain a broken session control.

devhub 0.102.0 was discovered to contain a broken session control.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-41542 describes broken session control in devhub 0.102.0. In business terms, a valid user session may not be handled safely, increasing the chance of unauthorized account access or actions if a session remains usable longer than intended. The CVSS score is medium, with limited confidentiality and integrity impact and no availability impact.

Executive priority

Treat this as a moderate identity and session-management risk. Prioritize confirmation of DevHub usage and vendor remediation status over emergency response, unless internal review shows sensitive accounts, privileged access, or suspicious session activity.

Technical view

The CVE maps to CWE-613, insufficient session expiration, with CVSS 3.1 5.4: network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, low confidentiality and integrity impact. The source bundle does not identify exact affected CPEs, vendor metadata, patch versions, or concrete remediation details.

Likely exposure

Exposure is most plausible for organizations using devhub 0.102.0 or the referenced DevHub application. The CVE metadata lists affected vendor, product, versions, and CPEs as unavailable, so asset matching should rely on internal SaaS inventories and vendor confirmation.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public references include the DevHub sites and a researcher write-up, but the provided metadata does not establish real-world exploitation, exploit maturity, or weaponized tooling.

Researcher notes

Evidence is thin: the CVE record gives a short description, CWE-613, CVSS, and references, but no CPEs, patch notes, or detailed affected surface. Avoid expanding scope beyond devhub 0.102.0 without vendor or primary-source confirmation.

Mitigation direction

  • Check DevHub vendor guidance for fixed versions or configuration changes.
  • Upgrade or reconfigure only according to confirmed vendor instructions.
  • Review session timeout, logout, and account-change invalidation behavior.
  • Reduce session lifetime where administratively configurable.
  • Monitor account activity for unusual reuse of existing sessions.

Validation and detection

  • Confirm whether devhub 0.102.0 is used in your environment.
  • Review SaaS inventory, SSO logs, and procurement records for DevHub usage.
  • Ask the vendor to confirm affected builds and remediation status.
  • Test session expiration behavior in an authorized staging environment.
  • Check logs for abnormal session persistence or account activity.
Prepared
Confidence
medium
Sources
5

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-613: 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-2022-41542 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-41542Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

CVECVE Program Container
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-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.