CyberSecBulletin
CVE-2024-25729NVD status: Deferred

sbg6580: Weak Password Requirements

CVE-2024-25729 is a high-severity weak password requirements vulnerability in sbg6580 from Arris, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected sbg6580 versions: all versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of sbg6580 you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Arrissbg6580all versionsNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

Arris SBG6580 devices have predictable default WPA2 security passwords that could lead to unauthorized remote access. (They use the first 6 characters of the SSID and the last 6 characters of the BSSID, decrementing the last octet.)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Weak Password Requirements

The product does not require that users should have strong passwords.

How developers prevent this class of flaw

  • Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
  • Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.

More Weak Password Requirements vulnerabilities (CWE-521)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Weak Password Requirements vulnerabilities

Spotted an error? Tell us.