dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2023-49224

HIGH · 8.0 CVSS v3.1 Published 2024-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Precor touchscreen console P62, P80, and P82 contains a default SSH public key in the authorized_keys file. A remote attacker could use this key to gain root privileges.

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

Precor P62, P80, and P82 touchscreen fitness consoles contain a hardcoded/default SSH public key stored in the authorized_keys file. An attacker with the corresponding private key can remotely authenticate as root to the affected device.

MitigationRemove the default SSH public key from the authorized_keys file, replace with organization-specific keys, or disable SSH entirely if not required for device management.

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

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

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 console model
    Determine if the device is a Precor P62, P80, or P82 touchscreen fitness console by checking the device label, boot splash screen, or system information
    Affected if Device is one of the three affected models (P62, P80, P82)
  2. Confirm SSH is enabled
    Check if SSH service is running on the console (e.g., run 'ps aux | grep sshd' or check startup services)
    Affected if SSH daemon is active and accepting connections
  3. Locate authorized_keys file
    Examine the SSH authorized_keys file, typically found at /root/.ssh/authorized_keys or /home/<user>/.ssh/authorized_keys
    Affected if File exists and contains public key entries
  4. Identify default key presence
    Review the authorized_keys content for any default, vendor-supplied, or hardcoded SSH public keys
    Affected if Default or vendor-supplied SSH public key is present in the authorized_keys file

Device is affected if it is a Precor P62, P80, or P82 console with SSH enabled and a default SSH public key present in the authorized_keys file, allowing remote root authentication with the corresponding private key.

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

Remove the default SSH public key from the authorized_keys file, replace with organization-specific keys, or disable SSH entirely if not required for device management.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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