dbcve.org
Course ManagerApplication · Golfbuddyglobal

CVE-2020-9337

MEDIUM · 6.5 CVSS v3.1 Published 2020-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In GolfBuddy Course Manager 1.1, passwords are sent (with base64 encoding) via a GET request.

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

GolfBuddy Course Manager 1.1 transmits user passwords using GET requests with only base64 encoding. Base64 is encoding, not encryption, so passwords are easily reversible. Additionally, GET requests expose credentials in URLs, server logs, browser history, and proxy logs.

MitigationMigrate authentication to use POST requests over HTTPS and implement proper password handling with server-side verification (e.g., salted hashes) rather than transmitting raw passwords.

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
Course ManagerApplication
Affected:= 1.1

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. Identify GolfBuddy Course Manager installation
    Search for GolfBuddy Course Manager executable or installed program on the system
    Affected if GolfBuddy Course Manager version 1.1 is installed
  2. Confirm installed version is 1.1
    Check application version in file properties, about dialog, or installed programs list
    Affected if Version displayed is exactly 1.1
  3. Capture login network traffic
    Use network sniffer (Wireshark) or browser developer tools to capture traffic during application login
    Affected if HTTP GET requests are used for authentication
  4. Verify credentials are base64 only
    Decode observed credential values in captured traffic using any base64 decoder
    Affected if Password values are reversible base64 strings rather than hashes
  5. Check logs for exposed credentials
    Review web server access logs, proxy logs, and browser history for login-related URLs
    Affected if Base64-encoded passwords appear in URL query strings in any logs

Environment is affected if GolfBuddy Course Manager version 1.1 is installed and uses GET requests with base64-encoded passwords transmitted in URLs.

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

Migrate authentication to use POST requests over HTTPS and implement proper password handling with server-side verification (e.g., salted hashes) rather than transmitting raw passwords.

Fix this in Course Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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