dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-41380

MEDIUM · 6.1 CVSS v4.0 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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
Iridium Certus 700 version 1.0.1 has an embedded credentials vulnerability in the code. This vulnerability allows a local user to retrieve the SSH hash string.

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

Iridium Certus 700 firmware version 1.0.1 contains hardcoded/embedded SSH credentials in the code itself. A local user with access to the device or firmware can retrieve the SSH hash string, enabling authentication as the embedded user.

MitigationRemove embedded credentials from firmware code and rotate exposed SSH credentials immediately. Apply vendor firmware patch when available and implement credential management controls to prevent future hardcoded secrets.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 the Iridium Certus 700 firmware version
    Access the device management interface or extract firmware and check the version string. Common methods: log into the device admin panel, check system information page, or use tools like binwalk to extract firmware and search for version metadata files.
    Affected if The installed firmware version is 1.0.1 (the affected version).
  2. Locate SSH service configuration
    Check if SSH daemon (sshd) is enabled and running on the device. Use commands like 'ps aux | grep sshd', check /etc/ssh/sshd_config, or review network listening services.
    Affected if SSH service is active and accessible on the device.
  3. Extract and inspect firmware for embedded credentials
    If you have firmware binary access (device filesystem, firmware update file, or physical flash extraction), search for hardcoded credential patterns. Use tools like strings, grep, or binwalk to extract readable strings from the firmware image. Look for SSH-related strings such as 'ssh', 'authorized_keys', password hashes, or RSA/DSA private keys embedded in binary data.
    Affected if Binary analysis reveals SSH private keys, password hashes, or credential strings that are hardcoded within the firmware code rather than configured by the administrator.
  4. Check for undocumented SSH users
    Compare the list of valid SSH users on the system (via /etc/passwd, /etc/shadow, or device user database) against expected/legitimate users. Look for accounts that are not documented in administrator guides.
    Affected if An undocumented or hidden SSH user account exists on the system.

Your environment is affected if the Iridium Certus 700 device runs firmware version 1.0.1 and contains embedded SSH credentials or undocumented SSH accounts in the firmware or device filesystem.

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 embedded credentials from firmware code and rotate exposed SSH credentials immediately. Apply vendor firmware patch when available and implement credential management controls to prevent future hardcoded secrets.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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