[Snyk] Security upgrade org.bouncycastle:bcpkix-jdk18on from 1.74 to 1.78 - #7
Open
spolti wants to merge 42 commits into
Open
[Snyk] Security upgrade org.bouncycastle:bcpkix-jdk18on from 1.74 to 1.78#7spolti wants to merge 42 commits into
spolti wants to merge 42 commits into
Conversation
Upstream Sync November 8th 2022
[pull] main from kserve:main
[pull] main from kserve:main
Merge from upstream 0.11.0-alpha
Signed-off-by: jooho <jlee@redhat.com>
Add modelmesh version
Signed-off-by: Selbi <43946617+heyselbi@users.noreply.github.com>
Updating owners to current maintainers
Signed-off-by: Selbi <43946617+heyselbi@users.noreply.github.com>
Signed-off-by: Jooho Lee <jlee@redhat.com>
Sync between RHODS and ODH
Signed-off-by: jooho <jlee@redhat.com>
add develop files for openshift-ci
Signed-off-by: jooho <jlee@redhat.com>
add develop files for openshift-ci
Dockerfile.develop file in modelmesh-serving is updated. This is required to execute modelmesh-serving openshift ci Signed-off-by: Jooho Lee <jlee@redhat.com>
Update Dockerfile.develop for modelmesh-serving
Signed-off-by: jooho <jlee@redhat.com>
…for openshift-ci and update version Signed-off-by: jooho <jlee@redhat.com>
[Sync] kserve/modelmesh-v0.11.0-rc0 to main branch
Signed-off-by: Vaibhav Jain <vajain@redhat.com>
[pull] main from kserve:main
In openshift-ci, only static values can be passed when building a
Dockerfile. However, the `imageVersion`, `buildId` and `commitSha` are
required to be generated when doing the build (are dynamic); e.g:
```
GIT_COMMIT=$(git rev-parse HEAD)
BUILD_ID=$(date '+%Y%m%d')-$(git rev-parse HEAD | cut -c -5)
IMAGE_TAG_VERSION=0.11.0-alpha
IMAGE_TAG=${IMAGE_TAG_VERSION}-$(git branch --show-current)_${BUILD_ID}
podman build \
--build-arg imageVersion=${IMAGE_TAG} \
--build-arg buildId=${BUILD_ID} \
--build-arg commitSha=${GIT_COMMIT} .
```
The most important argument is `buildId` to let ModelMesh identify the
build date of itself.
This changes the Dockerfile to resolve the `buildId` in the builder
stage. The `imageVersion` and `commitSha` arguments are lost, under the
rationale that these are not essential for ModelMesh to work correctly.
Signed-off-by: Edgar Hernández <23639005+israel-hdez@users.noreply.github.com>
Adjust Dockerfile to be more friendly with openshift-ci
Remove files that are no longer needed for CI. Signed-off-by: Edgar Hernández <23639005+israel-hdez@users.noreply.github.com>
This reverts commit de7836a.
Sync main with upstream
Signed-off-by: Spolti <fspolti@redhat.com>
add new members to the OWNERS file
Signed-off-by: Spolti <fspolti@redhat.com>
[RHODS-12555] - CVE-2023-44487
chore: update ubi8-minimal to latest version, 8.8. Vulnerabities fixed: - [RHSA-2023:7165]( https://access.redhat.com/errata/RHSA-2023:7151): cups security and bug fix update (Moderate) - [RHSA-2023:7151](https://access.redhat.com/errata/RHSA-2023:7151): python3 security update (Moderate) - [RHSA-2023:7176](https://access.redhat.com/errata/RHSA-2023:7176): python-pip security update (Moderate) - [RHSA-2023:7176](https://access.redhat.com/errata/RHSA-2023:7176): python-pip security update (Moderate) - [RHSA-2023:7151](https://access.redhat.com/errata/RHSA-2023:7151): python3 security update (Moderate) - [RHSA-2023:7190](https://access.redhat.com/errata/RHSA-2023:7190): avahi security update (Moderate) - [RHSA-2023:7112](https://access.redhat.com/errata/RHSA-2023:7112): shadow-utils security and bug fix update (Low) Signed-off-by: Spolti <fspolti@redhat.com>
chore: Update bouncy castle depdendency to address the following vulnerability: - [CVE-2023-33201](https://nvd.nist.gov/vuln/detail/CVE-2023-33201): Bouncy Castle For Java LDAP injection vulnerability Signed-off-by: Spolti <fspolti@redhat.com>
Address bounce castle cve alert
Bump ubi8 tag to 8.8
Signed-off-by: Spolti <fspolti@redhat.com>
[pull] main from kserve:main
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-6612984 - https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-6613076 - https://snyk.io/vuln/SNYK-JAVA-ORGBOUNCYCASTLE-6613079
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
With an upgrade:
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
SNYK-JAVA-ORGBOUNCYCASTLE-6612984
org.bouncycastle:bcpkix-jdk18on:1.74 -> 1.78Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.9
SNYK-JAVA-ORGBOUNCYCASTLE-6613076
org.bouncycastle:bcpkix-jdk18on:1.74 -> 1.78Why? Recently disclosed, Has a fix available, CVSS 5.3
SNYK-JAVA-ORGBOUNCYCASTLE-6613079
org.bouncycastle:bcpkix-jdk18on:1.74 -> 1.78(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling