CVE-2025-14808
Received Received - Intake
Information Disclosure via HTTP GET Query in IBM InfoSphere

Publication date: 2026-03-25

Last updated on: 2026-03-26

Assigner: IBM Corporation

Description
IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 could allow an attacker to obtain sensitive information from the query string of an HTTP GET method to process a request which could be obtained using man in the middle techniques.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-25
Last Modified
2026-03-26
Generated
2026-05-07
AI Q&A
2026-03-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ibm infosphere_information_server From 11.7.0.0 (inc) to 11.7.1.6 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-598 The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in IBM InfoSphere Information Server allows sensitive information to be exposed via the query string in HTTP GET requests, which can be intercepted through man-in-the-middle attacks.

Such exposure of sensitive information could potentially impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive data against unauthorized access and disclosure.

However, the provided information does not explicitly discuss compliance implications or how this vulnerability directly affects adherence to these standards.


Can you explain this vulnerability to me?

This vulnerability in IBM InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6 involves the use of the HTTP GET method to process requests that contain sensitive information in the query string.

Because the sensitive data is included in the URL query string, an attacker can intercept this information using man-in-the-middle techniques, potentially exposing confidential data.

This issue is classified under CWE-598: Use of GET Request Method With Sensitive Query Strings.


How can this vulnerability impact me? :

The vulnerability allows an attacker with network access to intercept sensitive information transmitted in the query string of HTTP GET requests.

The impact is considered low in terms of confidentiality (CVSS score 3.1), with no impact on integrity or availability.

However, if exploited, sensitive data exposure could lead to unauthorized information disclosure, which might affect privacy or security depending on the nature of the data.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should apply the fixes provided in IBM InfoSphere Information Server versions 11.7.1.0, 11.7.1.6, or the 11.7.1.6 Service Pack 2.

No workarounds or alternative mitigations are specified in the security bulletin.

It is also recommended to evaluate the impact of this vulnerability in your specific environment, as the CVSS environmental score may vary.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

The vulnerability involves sensitive information being exposed in the query string of HTTP GET requests processed by IBM InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6. Detection would involve monitoring network traffic for HTTP GET requests containing sensitive data in the query string.

To detect this on your network, you can use network traffic analysis tools such as Wireshark or tcpdump to capture HTTP GET requests to the affected server and inspect the query strings for sensitive information.

  • Using tcpdump to capture HTTP traffic on port 80 or 443 (if unencrypted): tcpdump -i <interface> -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)'
  • Using Wireshark, apply a display filter for HTTP GET requests: http.request.method == "GET" and inspect the query strings for sensitive data.

Note that if HTTPS is used, decrypting traffic is necessary to inspect query strings, which may require access to server keys or use of a proxy.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart