dbcve.org
Galaxy Buds ManagerApplication · Samsung

CVE-2024-20887

HIGH · 7.5 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 2.1.240315.51 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Arbitrary directory creation in GalaxyBudsManager PC prior to version 2.1.240315.51 allows attacker to create arbitrary directory.

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

Arbitrary directory creation vulnerability in GalaxyBudsManager PC software versions prior to 2.1.240315.51 allows an attacker to create directories in unintended locations on the file system, likely due to insufficient input validation on path parameters.

MitigationUpgrade GalaxyBudsManager PC to version 2.1.240315.51 or later to obtain the patch.

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
Galaxy Buds ManagerApplication
Affected:< 2.1.240315.51

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Galaxy Buds Manager is installed
    Check if GalaxyBudsManager exists on the system by searching for the application in installed programs (Add or Remove Programs on Windows) or locating the executable file (commonly in Program Files or Program Files (x86) directories under a Samsung or GalaxyBuds folder)
    Affected if Galaxy Buds Manager is found installed on the system
  2. Determine installed version number
    Right-click on the GalaxyBudsManager executable or its shortcut, select Properties, and view the Details tab to find the Product Version field. Alternatively, view the version shown in Add or Remove Programs for Galaxy Buds Manager
    Affected if Unable to determine the version number from the application or installed programs list
  3. Compare version against vulnerable range
    Compare your identified version to the affected version threshold: 2.1.240315.51. Any version number lower than 2.1.240315.51 (such as 2.1.x, 2.0.x, or earlier) falls within the vulnerable range
    Affected if Installed version is less than 2.1.240315.51 (for example, 2.1.240220.41 or any earlier release)
  4. Confirm vulnerability requires directory creation feature
    The vulnerability allows arbitrary directory creation through insufficient input validation on path parameters. This means the flaw is triggered when the application processes user-supplied path inputs, typically during device sync, firmware update, or file transfer operations that create folders on the PC
    Affected if The vulnerable version (below 2.1.240315.51) is in use and the application is actively used for Galaxy Buds management tasks

You are affected if Galaxy Buds Manager PC software is installed and the version is lower than 2.1.240315.51.

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 2.1.240315.51 or later
Fixed in 2.1.240315.51
Interim mitigation

Upgrade GalaxyBudsManager PC to version 2.1.240315.51 or later to obtain the patch.

Recommended fix High confidence

2.1.240315.51 or later

  1. 1. Ensure Galaxy Buds Manager is not currently running
  2. 2. Download Galaxy Buds Manager version 2.1.240315.51 or later from the official Samsung website or Galaxy Buds Manager download page
  3. 3. Run the installer and follow the on-screen prompts to upgrade
  4. 4. Verify the installed version by checking About/Version information in the application

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

Fix this in Galaxy Buds Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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