dbcve.org
Asik Airscale 474021a.102 FirmwareOperating system · Nokia

CVE-2022-2482

HIGH · 8.8 CVSS v3.1 Published 2023-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
A vulnerability exists in Nokia’s ASIK AirScale system module (versions 474021A.101 and 474021A.102) that could allow an attacker to place a script on the file system accessible from Linux. A script placed in the appropriate place could allow for arbitrary code execution in the bootloader.

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

A vulnerability in Nokia ASIK AirScale system module versions 474021A.101 and 474021A.102 allows an attacker to place a malicious script on the Linux-accessible file system, which can then be executed to achieve arbitrary code execution in the bootloader context.

MitigationApply vendor-supplied firmware patches when available; otherwise, restrict physical and network access to the system module to prevent unauthorized script placement on the file system.

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
Asik Airscale 474021a.102 FirmwareOperating system
Affected:all versions
Asik Airscale 474021a.101 FirmwareOperating system
Affected:all versions

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 Nokia ASIK AirScale firmware version
    Query the system module for its firmware version using the vendor-provided management interface or CLI command (typically via 'show version' or system information page). Record the exact firmware identifier shown (e.g., 474021A.101 or 474021A.102).
    Affected if The displayed firmware version is 474021A.101 or 474021A.102 (all versions of these releases are affected).
  2. Confirm the hardware model identifier
    Locate the system module hardware label or management interface display showing the product identifier (474021A.xxx). Ensure the model matches the affected product family.
    Affected if The hardware model identifier begins with 474021A.101 or 474021A.102.
  3. Assess physical access to the system module
    Determine whether unauthorized personnel can physically access the Nokia ASIK AirScale hardware unit to insert media or connect storage devices to the Linux-accessible file system.
    Affected if Physical access is not adequately restricted, allowing potential script placement on accessible filesystem locations.
  4. Assess network exposure of the filesystem interface
    Review network configuration and access controls to determine if the Linux-accessible file system (or associated management ports) is exposed to untrusted network segments or the internet.
    Affected if The filesystem or management interface is accessible over the network without proper authentication or network segmentation.
  5. Inspect for unexpected script files
    If filesystem access is available, enumerate script and executable file locations on the Linux-accessible file system. Compare against known-good baseline or vendor documentation of expected files.
    Affected if Any unexpected or unauthorized script files are present that were not deployed by the administrator or vendor.

You are affected if your Nokia ASIK AirScale system module runs firmware version 474021A.101 or 474021A.102 AND the Linux-accessible file system is exposed to unauthorized physical or network access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches when available; otherwise, restrict physical and network access to the system module to prevent unauthorized script placement on the file system.

Fix this in Asik Airscale 474021a.102 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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