Safeguard
Vulnerability Analysis•

CVE-2022-43845: Low Cookie Flag Issue in IBM Aspera Console

CVE-2022-43845 is a low (3.7) missing HTTPOnly cookie flag in IBM Aspera Console 3.4.0 through 3.4.4. IBM fixes it in version 3.4.5, so plan the upgrade.

Safeguard Security Team
3 min read

CVE-2022-43845 is a low severity (CVSS 3.7) issue in IBM Aspera Console 3.4.0 through 3.4.4, where a cookie is set without the HTTPOnly flag. A remote attacker could read sensitive information from the cookie. IBM remediates it in version 3.4.5, along with several other issues.

What's affected

The record lists IBM Aspera Console 3.4.0 through 3.4.4. IBM's security bulletin says the vulnerabilities it covers were remediated in IBM Aspera Console 3.4.5, and it offers downloads for Windows and Linux. The bulletin lists no workarounds.

The record scores the flaw 3.7 (Low) with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, and IBM's bulletin agrees on 3.7. The classes in the record are CWE-1004 (Sensitive Cookie Without HttpOnly Flag) and CWE-732 (Incorrect Permission Assignment for Critical Resource). The bulletin is dated 23 September 2024.

The same bulletin covers other issues in the product, including an XPath injection and a cross-site scripting issue, so the upgrade to 3.4.5 does more than this one fix.

How to check if you're exposed

Check the Aspera Console version in the web interface or in your deployment records. Anything from 3.4.0 through 3.4.4 is in the affected range.

You can also check the cookie flag from the outside, because a response header shows it. Using curl against your own console, look at the cookie lines in the response headers and see whether HttpOnly appears:

curl -sI https://YOUR-CONSOLE-HOST/ | grep -i set-cookie

Only run this against systems you own. A missing HttpOnly flag on a session cookie confirms the weakness in practice.

What to do now

  1. Find your Aspera Console instances and their versions.
  2. Plan the upgrade to 3.4.5, which IBM names as the remediating release, and download the Linux or Windows build from IBM's bulletin.
  3. Put the console behind TLS and restrict who can reach it.
  4. Review whether any other script on the console's pages is untrusted, since the HttpOnly flag matters mainly when a script can run in the page.
  5. Record the version in your inventory.

Why it matters

The HttpOnly flag tells the browser to keep a cookie out of reach of page scripts. Without it, any script that runs in the page, for example through a cross-site scripting bug, can read the cookie. For a session cookie that can mean session theft.

On its own the flag is a hardening setting, which is why the score is low and the attack complexity high: an attacker needs a second bug to make use of it. The bulletin lists a cross-site scripting issue in the same product, which shows how small issues can combine. The record's KEV flag is false and the bulletin does not report exploitation.

Quick check

Is a missing HttpOnly flag a vulnerability on its own?

It is a weakness that matters when another flaw lets a script run in the page. The low score reflects that dependency.

Which version fixes it?

IBM's bulletin names 3.4.5.

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.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.