dbcve.org
Acera 1310 FirmwareOperating system · Furunosystems

CVE-2023-39222

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 02.36 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
OS command injection vulnerability in FURUNO SYSTEMS wireless LAN access point devices allows an authenticated user to execute an arbitrary OS command that is not intended to be executed from the web interface by sending a specially crafted request. Affected products and versions are as follows: ACERA 1320 firmware ver.01.26 and earlier, ACERA 1310 firmware ver.01.26 and earlier, ACERA 1210 firmware ver.02.36 and earlier, ACERA 1150i firmware ver.01.35 and earlier, ACERA 1150w firmware ver.01.35 and earlier, ACERA 1110 firmware ver.01.76 and earlier, ACERA 1020 firmware ver.01.86 and earlier, ACERA 1010 firmware ver.01.86 and earlier, ACERA 950 firmware ver.01.60 and earlier, ACERA 850F firmware ver.01.60 and earlier, ACERA 900 firmware ver.02.54 and earlier, ACERA 850M firmware ver.02.06 and earlier, ACERA 810 firmware ver.03.74 and earlier, and ACERA 800ST firmware ver.07.35 and earlier. They are affected when running in ST(Standalone) mode.

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

OS command injection vulnerability in FURUNO SYSTEMS ACERA series wireless LAN access points allows authenticated attackers to execute arbitrary OS commands via specially crafted web interface requests. The vulnerability exists only when devices operate in ST (Standalone) mode and requires valid user credentials for exploitation.

MitigationApply available firmware updates to all affected ACERA models (specific versions listed in CVE) and restrict web interface access to trusted users only until patching is complete.

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
Acera 1310 FirmwareOperating system
Affected:<= 01.26
Acera 1320 FirmwareOperating system
Affected:<= 01.26
Acera 1210 FirmwareOperating system
Affected:<= 02.36
Acera 1150i FirmwareOperating system
Affected:<= 01.35
Acera 1150w FirmwareOperating system
Affected:<= 01.35
Acera 1110 FirmwareOperating system
Affected:<= 01.76
Acera 1020 FirmwareOperating system
Affected:<= 01.86
Acera 1010 FirmwareOperating system
Affected:<= 01.86

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 ACERA model
    Locate the device model identifier in the web interface status page, device label, or administrative console. Common locations include the System Information or Device Status section.
    Affected if The model is one of: Acera 1310, 1320, 1210, 1150i, 1150w, 1110, 1020, or 1010
  2. Check the installed firmware version
    Navigate to the firmware version information in the web administrative interface, typically found under System Settings, Maintenance, or Device Information. Compare the displayed version number against the affected ranges provided.
    Affected if The firmware version is at or below: 01.26 for models 1310/1320, 02.36 for model 1210, 01.35 for models 1150i/1150w, 01.76 for model 1110, or 01.86 for models 1020/1010
  3. Verify the device operating mode
    Access the network or system settings in the web interface and locate the operational mode configuration. Look for a setting that indicates ST, Standalone, or Access Point mode.
    Affected if The device is configured to operate in ST (Standalone) mode as the sole operating mode
  4. Confirm web interface accessibility
    Determine if the web administrative interface is reachable from the network. This can be verified by attempting to access the device IP on ports 80 or 443, or by reviewing access control lists, firewall rules, or network segmentation configurations.
    Affected if The web interface is accessible from network segments beyond trusted administrative hosts

The environment is affected if the device is an ACERA model within the specified firmware version ranges, is operating in ST (Standalone) mode, and has its web interface accessible to the attacker.

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 a release after 02.36
Interim mitigation

Apply available firmware updates to all affected ACERA models (specific versions listed in CVE) and restrict web interface access to trusted users only until patching is complete.

Recommended fix Moderate confidence

Firmware versions greater than: 01.26 (1310/1320), 02.36 (1210), 01.35 (1150i/1150w), 01.76 (1110), 01.86 (1020/1010) - obtain exact fixed releases from FURUNO SYSTEMS

  1. 1. Identify the specific Acera model in use (e.g., Acera 1310, 1320, 1210, 1150i, 1150w, 1110, 1020, or 1010).
  2. 2. Verify the current firmware version through the device's web interface or administrative console.
  3. 3. Confirm the device is operating in ST (Standalone) mode, as this vulnerability only affects that mode.
  4. 4. Download the latest firmware version from the official FURUNO SYSTEMS support website (www.furunosystems.co.jp).
  5. 5. Back up the current device configuration before performing the firmware update.
  6. 6. Access the device's administrative web interface and navigate to the firmware upgrade section.
  7. 7. Upload and install the updated firmware file, following the manufacturer's upgrade instructions.
  8. 8. After the firmware update completes, verify the new version is installed correctly.
Caveat Review release notes for any configuration or feature changes between current and upgraded firmware versions; backup configuration before upgrade

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

Fix this in Acera 1310 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA4.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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