dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-56083

HIGH · 8.1 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cognition Devin before 2024-12-12 provides write access to code by an attacker who discovers the https://vscode-randomly_generated_string.devinapps.com URL (aka the VSCode live share URL) for a specific "Use Devin's Machine" session. For example, this URL may be discovered if a customer posts a screenshot of a Devin session to social media, or publicly streams their Devin session.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability stems from insufficient randomness in VSCode live share URLs for Devin sessions. An attacker who discovers the URL (e.g., from social media screenshots or streams) gains write access to the victim's code. The URL format uses predictable randomness that can be brute-forced or simply found in public posts.

MitigationRegenerate session URLs with cryptographically secure randomness (e.g., UUID v4 or longer entropy), implement URL expiration, add authentication layers for session access, and educate users about not exposing session URLs publicly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify VSCode Live Share extension is installed
    Check the VSCode extensions panel or list installed extensions via command palette (Extensions: List Extensions) for 'Live Share' extension
    Affected if The Live Share extension is present and active in the VSCode environment
  2. Examine live share session URL format
    Start a live share session in VSCode (via Live Share button in bottom-left or Ctrl+Shift+P > 'Live Share: Start Session') and inspect the generated URL in the sharing dialog
    Affected if The session URL contains fewer than 22 random characters or uses a predictable pattern (e.g., sequential numbers, base64 strings shorter than 128 bits)
  3. Check for URL entropy in active sessions
    If a live share session is active, use the Live Share activity bar to view session details and copy the guest link; analyze the character set and length of the URL segment after the last slash
    Affected if The URL segment contains fewer than 16 high-entropy random characters or appears to use timestamp-derived values
  4. Scan for publicly exposed session URLs
    Search your organization's public channels, social media posts, shared screenshots, or recorded streams for patterns matching 'liveshare.vscode.com' or similar live share URL formats
    Affected if Any live share session URLs are found in publicly accessible locations such as social media, shared images, or recorded content
  5. Review session access controls
    In VSCode Live Share settings (File > Preferences > Settings > Live Share), check if 'Require authentication for guest access' is enabled or if session expiration is configured
    Affected if No authentication is required for joining sessions and no session expiration is set

Users are affected if they generate live share URLs with insufficient randomness and those URLs become publicly visible, allowing unauthorized write access to their code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Regenerate session URLs with cryptographically secure randomness (e.g., UUID v4 or longer entropy), implement URL expiration, add authentication layers for session access, and educate users about not exposing session URLs publicly.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56083 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-56083 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data