dbcve.org
AleosOperating system · Sierrawireless

CVE-2023-40460

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-04
Fix available
A fix is available. Upgrade to after 4.16.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The ACEManager component of ALEOS 4.16 and earlier does not validate uploaded file names and types, which could potentially allow an authenticated user to perform client-side script execution within ACEManager, altering the device functionality until the device is restarted.

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

The ACEManager component in ALEOS 4.16 and earlier fails to validate uploaded file names and types, allowing authenticated users to upload malicious files containing client-side scripts that execute within the ACEManager interface, creating a stored XSS condition that persists until device restart.

MitigationRestrict ACEManager access to trusted, authenticated users only; contact ALEOS vendor for patched firmware version; implement strict file type and name validation on all upload endpoints.

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
AleosOperating system
Affected:<= 4.16.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 ALEOS version
    Access the device console or web interface and retrieve the firmware/OS version information. On most Sierra Wireless devices, this can be found in the ACEManager web interface under 'Device Information' or via the CLI command 'show system info' or 'get ver'. Compare the displayed version to the affected range (4.16.0 and earlier).
    Affected if The displayed ALEOS version is 4.16.0 or lower.
  2. Confirm ACEManager is enabled
    Access the device web interface and navigate to the ACEManager portal (typically at /acemanager or /admin). Verify the service is accessible and responding. Check device configuration for ACEManager service status via CLI using 'aceman show status' or checking the web server configuration.
    Affected if ACEManager web interface is accessible and responds to requests.
  3. Verify authentication is configured for ACEManager
    Check whether ACEManager requires authentication by attempting to access the login page. Review the device's user authentication settings in the ACEManager configuration under 'Users' or 'Access Control'. Determine if local or remote authentication (RADIUS, LDAP) is enabled.
    Affected if ACEManager accepts authenticated user credentials and provides access to the interface after login.
  4. Check for file upload functionality
    Within the ACEManager web interface, navigate to sections that accept file uploads such as configuration backup/restore, firmware updates, certificate management, or custom file uploads. Document which upload endpoints exist and whether they perform validation on file names and types.
    Affected if Any ACEManager page accepts file uploads without apparent validation of file name or content type.

The environment is affected if it runs Sierrawireless Aleos firmware version 4.16.0 or earlier AND has ACEManager enabled with authenticated access and file upload functionality present.

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 4.16.0
Interim mitigation

Restrict ACEManager access to trusted, authenticated users only; contact ALEOS vendor for patched firmware version; implement strict file type and name validation on all upload endpoints.

Recommended fix Moderate confidence

ALEOS version higher than 4.16.0 (contact Sierra Wireless for exact fixed release)

  1. 1. Identify all devices running ALEOS firmware version 4.16.0 or earlier
  2. 2. Access the ACEManager interface on each affected device
  3. 3. Navigate to the firmware management or system update section
  4. 4. Check for available firmware updates through the device's admin interface or Sierra Wireless's official support portal (source.sierrawireless.com)
  5. 5. Download and apply the latest ALEOS firmware version available from Sierra Wireless
  6. 6. After firmware update, verify the ACEManager component properly validates uploaded file names and types
  7. 7. Restart the device as recommended after firmware updates
  8. 8. Confirm the XSS vulnerability is remediated by testing file upload functionality
Caveat Review Sierra Wireless release notes for any configuration or compatibility changes between 4.16.0 and the target upgrade version

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

Fix this in Aleos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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