CVE-2022-38789
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 · uneditedAn issue was discovered in Airties Smart Wi-Fi before 2020-08-04. It allows attackers to change the main/guest SSID and the PSK to arbitrary values, and map the LAN, because of Insecure Direct Object Reference.
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 confidenceAn Insecure Direct Object Reference (IDOR) vulnerability in Airties Smart Wi-Fi devices before August 2020 allows unauthenticated remote attackers to arbitrarily modify the main and guest SSID names and pre-shared keys (PSK), and perform LAN reconnaissance to map the internal network.
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< 2020-08-04< 2020-08-04< 2020-08-04CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the Airties router web interface (typically at 192.168.1.1) and navigate to the Status or Firmware Information page. Note the exact model number (Air 4920, Air 4921, or Air 4971) and firmware build date.Affected if The device is an Air 4920, Air 4921, or Air 4971 with firmware dated before August 4, 2020 (build date earlier than 2020-08-04)
-
Verify web management interface exposureCheck router firewall settings to determine if HTTP (port 80) or HTTPS (port 443) management interfaces are accessible from WAN/external networks. This can be done by reviewing port forwarding rules, DMZ settings, or attempting an external connection test.Affected if The web management interface is exposed to untrusted networks (internet-facing) without VPN or IP restrictions
-
Review SSID configuration for unauthorized changesLog into the router web interface and navigate to Wireless Settings. Compare the current main SSID and guest SSID names against documented or expected values. Note any unknown or unexpected network names.Affected if Current SSID names do not match the originally configured names, or unknown SSIDs are present
-
Check PSK configuration integrityIn the Wireless Settings section, verify that the pre-shared keys for both main and guest networks match the originally configured passwords. Look for any changes that were not authorized.Affected if Current PSKs differ from the originally set passwords, or additional unknown PSKs are configured
-
Examine logs for unauthorized access attemptsAccess the router logs or system logs via the web interface (typically under Administration or Diagnostics). Search for POST requests to wireless configuration endpoints or repeated unauthenticated API calls.Affected if Logs show unexpected configuration change requests, particularly to wireless settings endpoints, from unfamiliar IP addresses
A user is affected if they own an Air 4920, Air 4921, or Air 4971 device running firmware dated before August 2020, especially if the management interface is internet-accessible or unexpected wireless configuration changes are detected.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2020-08-04
Upgrade Airties Smart Wi-Fi firmware to a version released on or after 2020-08-04. If patching is not possible, implement network segmentation to isolate the device and monitor for unauthorized Wi-Fi configuration changes.
AirTies Smart Wi-Fi firmware 2020-08-04 or later (for Air 4920, Air 4921, Air 4971)
- Identify the current firmware version of the Air 4920, Air 4921, or Air 4971 device
- Access the device management interface (typically via web browser at the device's IP address)
- Navigate to the firmware update or system settings section
- Check if a firmware update is available from AirTies support resources
- If an update is available, download and apply the firmware version dated 2020-08-04 or later
- After updating, verify that the firmware version reflects a date on or after 2020-08-04
- Confirm the IDOR vulnerability is remediated by verifying that unauthorized SSID/PSK changes are no longer possible without proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38789 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38789 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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