dbcve.org
Sdg SmartosOperating system · Adtran

CVE-2024-31970

HIGH · 8.8 CVSS v3.1 Published 2024-07-24
Fix available
A fix is available. Upgrade to 12.1.3.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
AdTran SRG 834-5 HDC17600021F1 devices (with SmartOS 11.1.1.1 and fixed in Version 12.1.3.1) have SSH enabled by default, accessible both over the LAN and the Internet. During a window of time when the device is being set up, it uses a default username and password combination of admin/admin with root-level privileges. An attacker can exploit this window to gain unauthorized root access by either modifying the existing admin account or creating a new account with equivalent privileges. This vulnerability allows attackers to execute arbitrary commands. NOTE: The vendor has disputed this, finding the report not applicable. According to AdTran, SSH has never been accessible (from WAN) on SmartOS official builds. Furthermore, the vendor adds that test build 11.1.0.101-202106231430 was never released to end users.

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

AdTran SRG 834-5 devices running SmartOS 11.1.1.1 have SSH enabled by default with accessible LAN and WAN interfaces. During initial device setup, the default credentials admin/admin provide root-level privileges, allowing attackers to either modify the existing admin account or create new privileged accounts to execute arbitrary commands.

MitigationUpdate firmware to version 12.1.3.1 or later. Additionally, restrict SSH access via firewall rules to prevent WAN exposure and change default credentials immediately if SSH is required.

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
Sdg SmartosOperating system
Affected:< 12.1.3.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
High
Availability
High

CVSS:3.1/AV:N/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 the device model and SmartOS version
    Access the device administrative interface or check the system information page to confirm the device is an AdTran SRG series and record the SmartOS firmware version number
    Affected if The device is an AdTran SRG 834-5 or similar AdTran SDG device running SmartOS version lower than 12.1.3.1
  2. Verify if SSH service is enabled
    Check the device services or security settings to determine whether SSH has been intentionally enabled or remains at its default enabled state
    Affected if SSH service is currently enabled on the device
  3. Confirm SSH accessibility on WAN interface
    Review the network interface bindings or firewall configuration to determine if SSH is listening or accessible on the WAN (external) interface in addition to LAN
    Affected if SSH is accessible from the WAN interface rather than restricted to LAN only
  4. Test default credential validity
    Attempt to authenticate to the SSH service using the default credentials admin/admin, or verify if the admin account password has been changed from the factory default
    Affected if The default credentials admin/admin successfully authenticate and provide administrative access

The environment is affected if the device runs AdTran SmartOS version below 12.1.3.1 with SSH enabled and the default admin/admin credentials still active, particularly if SSH is exposed to the WAN interface.

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.

dbcve · scoped
Upgrade available Upgrade to 12.1.3.1 or later
Fixed in 12.1.3.1
Interim mitigation

Update firmware to version 12.1.3.1 or later. Additionally, restrict SSH access via firewall rules to prevent WAN exposure and change default credentials immediately if SSH is required.

Recommended fix Moderate confidence

SmartOS 12.1.3.1

  1. Verify current SmartOS version by running 'smattrun root /usr/sbin/version' or checking the system information
  2. Download SmartOS version 12.1.3.1 from the official AdTran support portal or authorized distribution channels
  3. Backup all critical configuration data and user accounts before performing the upgrade
  4. Apply the SmartOS upgrade following AdTran's standard firmware update procedures, typically via the web management interface or CLI using 'sm-update' command
  5. After upgrade, verify the system is running version 12.1.3.1
  6. Confirm SSH access controls are properly configured: disable SSH if not required, or restrict access to trusted IP addresses only via firewall rules
  7. Change default admin password immediately if still using admin/admin
  8. Verify no unauthorized accounts exist in the system
Caveat Refer to AdTran 12.1.3.1 release notes for any configuration or feature changes from previous versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sdg Smartos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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