CVE-2024-22316: IBM Sterling File Gateway improper access control

Published Nov 14, 2024
·
Updated

IBM Sterling File Gateway 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.1 could allow an authenticated user to perform unauthorized actions to another user's data due to improper access controls.

Other sources

IBM Sterling File Gateway could allow an authenticated user to perform unauthorized actions to another user's data due to improper access controls.

IBM

Affected Software

5 affected components
IBM Sterling File Gateway>=6.0.0.0<=6.1.2.5, >=6.2.0.0<=6.2.0.1
IBM Sterling File Gateway<=6.0.0.0 - 6.1.2.5
IBM Sterling File Gateway<=6.2.0.0 - 6.2.0.1
IBM Sterling File Gateway>=6.0.0.0<=6.1.2.5
IBM Sterling File Gateway>=6.2.0.0<=6.2.0.1

Event History

Nov 14, 2024
CVE Published
via IBM·12:00 AM
Jan 27, 2025
CVE Published
via MITRE·04:03 PM
Data Sourced
via MITRE·04:03 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-22316?

CVE-2024-22316 is classified as a medium severity vulnerability due to improper access controls in IBM Sterling File Gateway.

2

How do I fix CVE-2024-22316?

To fix CVE-2024-22316, you should upgrade IBM Sterling File Gateway to a patched version that resolves the access control issues.

3

Which versions of IBM Sterling File Gateway are affected by CVE-2024-22316?

CVE-2024-22316 affects IBM Sterling File Gateway versions from 6.0.0.0 to 6.1.2.5 and 6.2.0.0 to 6.2.0.1.

4

What types of actions can an authenticated user perform due to CVE-2024-22316?

An authenticated user could perform unauthorized actions on another user's data because of the improper access controls in place.

5

Is there a workaround for CVE-2024-22316 while waiting for the fix?

There is no specific workaround for CVE-2024-22316, and it is recommended to upgrade to avoid potential unauthorized access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203