CVE-2022-43842 is a high severity (CVSS 8.6) SQL injection in IBM Aspera Console 3.4.0 through 3.4.2. A remote attacker could view, add, modify or delete data in the back end database. IBM's fix is 3.4.2 patch level 7 for Linux and Windows, and the bulletin lists no workaround.
What's affected
IBM's bulletin lists IBM Aspera Console 3.4.0 through 3.4.2 Patch Level 6 as affected. The fixing version is IBM Aspera Console 3.4.2 PL7, with separate downloads for Linux and Windows. The bulletin states that there are no workarounds or mitigations.
The record scores the flaw 8.6 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L. IBM's bulletin gives the same base score using CVSS 3.0. No privileges and no user interaction are needed. The weakness class is CWE-89 (SQL Injection). The bulletin is dated 22 February 2024.
How to check if you're exposed
Check the version in the Aspera Console web interface or through your deployment records, and compare it with the affected range: 3.4.0 through 3.4.2 Patch Level 6. If you run 3.4.2, find out which patch level you are on, since PL7 is the fixed one. IBM's page lists the product by name and patch level, so use the same labels when you ask your platform team.
Then check exposure. Aspera Console is a management interface, so ask who can reach its web port. If it is reachable from the internet or a wide internal network, move it up your list.
What to do now
- Identify every Aspera Console instance and its version and patch level.
- Download and apply Aspera Console 3.4.2 PL7 for your platform from IBM's bulletin links.
- Restrict network access to the console's web interface to the networks and people who need it.
- Review web server and database logs for unusual queries or errors around the console, going back as far as you keep them.
- Note that IBM publishes later bulletins for this product, including one that remediates other issues in version 3.4.5. Plan to move to a current release.
Why it matters
SQL injection happens when an application builds a database query out of text it received from a user, without separating the data from the command. A crafted input can then change what the query does. IBM's description says an attacker could view, add, modify or delete information in the back end database, which matches the high confidentiality and lower integrity and availability impact in the score.
The reason this class stays on the critical list year after year is that the fix is boring and the mistake is easy: use parameterized queries everywhere. For a customer using a vendor product there is no code to fix, only a patch to apply, and with no workaround listed, patching is the only route. The record's KEV flag is false and the bulletin does not report exploitation.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a workaround?
The bulletin lists none. Apply the patch and limit network access in the meantime.
What is the fixed version?
3.4.2 Patch Level 7, with separate downloads for Linux and Windows.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.