CVE-2025-28389
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 · uneditedWeak password requirements in OpenC3 COSMOS v6.0.0 allow attackers to bypass authentication via a brute force attack.
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 confidenceOpenC3 COSMOS v6.0.0 contains weak password requirements that fail to enforce adequate complexity, length, or account lockout policies. This allows remote attackers to perform brute force attacks against the authentication mechanism to gain unauthorized access to the system. The critical CVSS score of 9.8 reflects the ease of exploitation and complete compromise possible once authentication is bypassed.
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= 6.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify OpenC3 COSMOS installationCheck if OpenC3 COSMOS is installed by looking for its installation directory, service, or by running 'openc3 --version' or 'cosmos --version' if CLI tools are availableAffected if OpenC3 COSMOS is not present on the system - this CVE does not apply
-
Confirm installed version is 6.0.0Check the installed version of OpenC3 COSMOS using the CLI command (e.g., 'openc3 --version', 'cosmos --version') or inspect the installed package metadataAffected if The installed version is exactly 6.0.0 - other versions may have different password policies
-
Inspect password policy configurationLocate and examine the password policy configuration files or settings within the OpenC3 COSMOS installation directory. Look for files related to authentication, password requirements, or user managementAffected if Password policy settings are absent, set to weak values (e.g., short minimum length, no complexity requirements), or not enforced
-
Check account lockout settingsReview authentication configuration for account lockout or account takeover protection settings. Look for failed login attempt thresholds and lockout durationsAffected if Account lockout is disabled or set to a high threshold/number of attempts, allowing brute force attacks
-
Verify brute force protectionExamine the authentication mechanism for rate limiting, CAPTCHA, or other brute force mitigations that may compensate for weak password policiesAffected if No brute force protection mechanisms are implemented or configured
The system is affected if it runs OpenC3 COSMOS version 6.0.0 and lacks adequate password complexity requirements, minimum length enforcement, and account lockout policies to prevent brute force attacks.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strong password policies enforcing minimum length, complexity requirements, and account lockout thresholds after failed attempts. Consider updating to a patched version if available and enabling multi-factor authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28389 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28389 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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