IBM Cognos Dashboards 4.0.7 and 5.0.0 on Cloud Pak for Data could allow a remote attacker to perform unauthorized actions due to dependency confusion.
IBM Cognos Dashboards on Cloud Pak for Data could allow a remote attacker to perform unauthorized actions due to dependency confusion.
Deep-merge could allow a remote attacker to execute arbitrary code on the system, caused by a prototype pollution flaw in the merge methods of lodash to merge objects. By adding or modifying properties of Object.prototype using a proto or constructor payload, an attacker could exploit this vulnerability to execute arbitrary code or cause a denial of service condition on the system.
Impact
Depending on network and process conditions of a fetch() request, response.arrayBuffer() might include portion of memory from the Node.js process.
Patches
This has been patched in v6.19.2.
Workarounds
There are no known workaround.
References
https://github.com/nodejs/undici/issues/3337 https://github.com/nodejs/undici/issues/3328 https://github.com/nodejs/undici/pull/3338 https://github.com/nodejs/undici/commit/f979ec3204ca489abf30e7d20e9fee9ea7711d36
IBM Cognos Dashboards exposes sensitive information in container images which could lead to further attacks against the system.
IBM Cognos Dashboards could allow a remote attacker to bypass security restrictions, caused by a reverse tabnabbing flaw. An attacker could exploit this vulnerability and redirect a victim to a phishing site.
IBM Cognos Dashboards exposes sensitive information in environment variables which could aid in further attacks against the system.
Last updated 24 July 2024
Advisory title: Issue with whitespace in JWT roles
Affected versions: OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1
Patched versions: OpenSearch 1.3.8 and 2.5.0
Impact: OpenSearch uses JWTs to store role claims obtained from the Identity Provider (IdP) when the authentication backend is SAML or OpenID Connect. There is an issue in how those claims are processed from the JWTs where the leading and trailing whitespace is trimmed, allowing users to potentially claim roles they are not assigned to if any role matches the whitespace-stripped version of the roles they are a member of.
This issue is only present for authenticated users, and it requires either the existence of roles that match, not considering leading/trailing whitespace, or the ability for users to create said matching roles. In addition, the Identity Provider must allow leading and trailing spaces in role names.
Patches: OpenSearch versions 1.3.8 and 2.5.0 contain a fix for this issue.
For more information: If you have any questions or comments about this advisory, please contact AWS/Amazon Security via our issue reporting page (https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Advisory title: Field-level security issue with .keyword fields
Affected versions: OpenSearch 1.0.0-1.3.7 and 2.0.0-2.4.1
Patched versions: OpenSearch 1.3.8 and 2.5.0
Impact: There is an issue in the implementation of field-level security (FLS) and field masking where rules written to explicitly exclude fields are not correctly applied for certain queries that rely on their auto-generated .keyword fields.
This issue is only present for authenticated users with read access to the indexes containing the restricted fields.
Workaround: FLS rules that use explicit exclusions can be written to grant explicit access instead. Policies authored in this way are not subject to this issue.
Patches: OpenSearch versions 1.3.8 and 2.5.0 contain a fix for this issue.
For more information: If you have any questions or comments about this advisory, please contact AWS/Amazon Security via our issue reporting page (https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.