dbcve.org
macOSOperating system · Apple

CVE-2024-44248

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 13.7.2 / 14.7.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
This issue was addressed through improved state management. This issue is fixed in macOS Sequoia 15.1, macOS Sonoma 14.7.2, macOS Ventura 13.7.2. A user with screen sharing access may be able to view another user's screen.

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 · moderate confidence

A state management flaw in macOS screen sharing allows a user with screen sharing access to potentially view another user's screen. The vulnerability stems from improper validation or synchronization of screen sharing session states, likely allowing session state to be manipulated or persisted incorrectly.

MitigationApply the macOS security updates (Ventura 13.7.2, Sonoma 14.7.2, or Sequoia 15.1) to all affected systems. Review screen sharing permissions and restrict access to only trusted users until patches are deployed.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
macOSOperating system
Affected:>= 13.0, < 13.7.2>= 14.0, < 14.7.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check macOS version
    Run 'sw_vers -productVersion' in Terminal to get the exact macOS version number
    Affected if The version is 13.0 to 13.7.1 inclusive, or 14.0 to 14.7.1 inclusive (the system is unpatched)
  2. Verify if Screen Sharing is enabled
    Go to System Settings > General > Sharing, or run 'sudo launchctl list | grep screensharing' to check if the Screen Sharing service is running
    Affected if Screen Sharing is turned on and the macOS version is in the affected range
  3. Check for active screen sharing sessions
    Run 'lsof -i :5900' in Terminal to see if any VNC connections (port 5900) are currently active, or check System Settings > General > Sharing > Screen Sharing for active connections
    Affected if There are active screen sharing connections while the system is unpatched
  4. Review screen sharing permission settings
    In System Settings > General > Sharing > Screen Sharing, verify which users are allowed access - check for 'Only these users' vs 'All users' setting
    Affected if Screen sharing access is granted to 'All users' or includes untrusted accounts on an unpatched system

A system is affected if it runs macOS Ventura 13.0-13.7.1 or Sonoma 14.0-14.7.1 with Screen Sharing enabled, regardless of whether active sessions are currently observed.

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.

dbcve · scoped
Upgrade available Upgrade to 13.7.2 / 14.7.2 or later
Fixed in 13.7.214.7.2
Interim mitigation

Apply the macOS security updates (Ventura 13.7.2, Sonoma 14.7.2, or Sequoia 15.1) to all affected systems. Review screen sharing permissions and restrict access to only trusted users until patches are deployed.

Recommended fix High confidence

macOS 13.7.2 (Ventura), macOS 14.7.2 (Sonoma), or macOS 15.1 (Sequoia)

  1. Back up your Mac before performing any system update
  2. Open System Settings and navigate to General > Software Update
  3. Install the available security update: macOS Ventura 13.7.2, macOS Sonoma 14.7.2, or macOS Sequoia 15.1 depending on your current macOS version
  4. Restart your Mac when prompted to complete the installation
  5. Verify the update was successful by checking System Settings > General > About for the version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44248 — 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-44248 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