Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump org.bouncycastle:bctls-fips from 1.0.18 to 1.0.19 in /bom/application #40642

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 14, 2024

Bumps org.bouncycastle:bctls-fips from 1.0.18 to 1.0.19.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps org.bouncycastle:bctls-fips from 1.0.18 to 1.0.19.

---
updated-dependencies:
- dependency-name: org.bouncycastle:bctls-fips
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels May 14, 2024
@quarkus-bot quarkus-bot bot added area/dependencies Pull requests that update a dependency file area/securepipeline issues related to ensure Quarkus can be used in a secure pipeline setups like FIPS or similar labels May 14, 2024
Copy link

quarkus-bot bot commented May 14, 2024

/cc @Karm (securepipeline), @jerboaa (securepipeline)

Copy link

quarkus-bot bot commented May 15, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 521f574.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.


Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging-kafka/deployment

io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase.sseStream - History

  • Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase Expecting size of: [] to be greater than or equal to 2 but was 0 within 10 seconds. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase 
Expecting size of:
  []
to be greater than or equal to 2 but was 0 within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)

@gsmet gsmet merged commit 3efdec8 into main May 15, 2024
51 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.11 - main milestone May 15, 2024
@dependabot dependabot bot deleted the dependabot/maven/bom/application/org.bouncycastle-bctls-fips-1.0.19 branch May 15, 2024 07:52
@gsmet
Copy link
Member

gsmet commented May 15, 2024

@sberyozkin @jmartisk apparently, this will fix a CVE. Not sure how far we should backport it.

@sberyozkin
Copy link
Member

@gsmet I'm not seeing any references to this bctls-fips, https://www.bouncycastle.org/latest_releases.html mentions non FIPS 1.78.1, which is covered with #40188, may be bctls-fips 1.0.19 copies some of the code from the non-FIPS base to handle some of those CVEs, in which case the backport can go to 3.8 at least

@sberyozkin
Copy link
Member

May be CVE 2024-34447, if non-FIPS version is impacted then the FIPS fork of BCTLS should be fixed too

@gsmet gsmet modified the milestones: 3.11.0.CR1, 3.10.2 May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file area/securepipeline issues related to ensure Quarkus can be used in a secure pipeline setups like FIPS or similar dependencies Pull requests that update a dependency file java Pull requests that update Java code kind/component-upgrade triage/flaky-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants