dbcve.org
Aspera FaspexApplication · Ibm

CVE-2023-22869

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 5.0.8 or later.
See remediation →
57/100
Remediation priority · Elevated
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
IBM Aspera Faspex 5.0.0 through 5.0.7 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 244119.

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

IBM Aspera Faspex versions 5.0.0 through 5.0.7 contains a vulnerability where the application stores potentially sensitive information in log files. A local user with access to the system could read these log files and obtain the sensitive data, leading to information disclosure.

MitigationImplement proper file permissions on log directories to restrict access to authorized administrators only. Additionally, review and sanitize sensitive data before logging, or upgrade to a version beyond 5.0.7 if a patched release is available.

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
Aspera FaspexApplication
Affected:>= 5.0.0, < 5.0.8

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Faspex version
    Run 'asadmin version' or check the Faspex About page in the web UI, or use package manager commands like 'rpm -q aspera-faspex' or 'dpkg -l aspera-faspex' depending on your OS
    Affected if Installed version is 5.0.0 through 5.0.7 (versions below 5.0.8 are affected)
  2. Locate Faspex log directories
    Check common log locations such as /opt/aspera/faspex/log/ or /var/log/aspera/faspex/ and any custom log paths configured in faspex.yml
    Affected if Log directories exist and contain log files from Faspex
  3. Verify log file permissions
    Run 'ls -la' on the log directories and check the ownership and permission bits (e.g., 'ls -la /opt/aspera/faspex/log/')
    Affected if Log files are readable by non-privileged users or group/other permissions include 'r'
  4. Examine log file contents for sensitive data
    Use commands like 'grep -i password' or 'grep -i token' on log files (e.g., 'cat /opt/aspera/faspex/logs/faspex.log | grep -i pass') to search for exposed credentials, API keys, or tokens
    Affected if Sensitive information such as passwords, API keys, tokens, or user credentials appear in plain text within log files

A user is affected if their installed Faspex version is 5.0.0 through 5.0.7 AND log files are accessible to unauthorized local users AND those logs contain sensitive information.

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 5.0.8 or later
Fixed in 5.0.8
Interim mitigation

Implement proper file permissions on log directories to restrict access to authorized administrators only. Additionally, review and sanitize sensitive data before logging, or upgrade to a version beyond 5.0.7 if a patched release is available.

Recommended fix High confidence

Aspera Faspex 5.0.8

  1. Verify current Aspera Faspex version by checking the application or system information
  2. Download Aspera Faspex version 5.0.8 from IBM Fix Central or official IBM distribution channels
  3. Review IBM Aspera upgrade documentation for version 5.0.8
  4. Perform a backup of the current Faspex installation, including configuration files and databases
  5. Stop the Aspera Faspex service before upgrading
  6. Install Aspera Faspex 5.0.8 following the documented upgrade procedure
  7. Verify the upgrade was successful by checking the version number
  8. Restart the Aspera Faspex service
Caveat Review IBM release notes for 5.0.8 for any configuration or feature changes that may require adjustment

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

Fix this in Aspera Faspex Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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