Skip to content

Conversation

@gpchandran
Copy link
Contributor

@gpchandran gpchandran commented Feb 13, 2025

There are few critical vulnerabilities that remain unresolved in the 3.11-slim-bookworm version. To address these , it is good to upgrade to the 3.11.11-slim-bookworm version
Hi @mistercrunch @michael-s-molina - can you please review and approve

#32229
#31503

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

here are few critical vulnerabilities that remain unresolved in the 3.11-slim-bookworm version. To address these security concerns, it is good  to upgrade to the 3.11.11-slim-bookworm version
Copy link

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've completed my review and didn't find any issues.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Documentation
Logging
Error Handling
Readability
Design
Performance
Security
Functionality

Feedback and Support

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️

We hope to see you in our Slack community too! Not signed up? Use our Slack App to self-register.

@michael-s-molina michael-s-molina changed the title Update Dockerfile - upgrade to 3.11.11-slim-bookworm fix: upgrade to 3.11.11-slim-bookworm to address critical vulnerabilities Feb 13, 2025
@michael-s-molina michael-s-molina added the v5.0 Label added by the release manager to track PRs to be included in the 5.0 branch label Feb 13, 2025
@michael-s-molina michael-s-molina merged commit ad05732 into apache:master Feb 13, 2025
51 of 53 checks passed
michael-s-molina pushed a commit that referenced this pull request Feb 14, 2025
dolph added a commit to dolph/superset that referenced this pull request Mar 13, 2025
Debian 11 bullseye is now the [oldstable release](https://www.debian.org/releases/), and Debian 12 bookworm is the current stable release. The release of node does not have to change at the same time.

This is a follow up to apache#32240
@gpchandran
Copy link
Contributor Author

gpchandran commented Mar 17, 2025

@sadpandajoe - is it possible to cherrypick this PR into 4.1.2rc1? this address lot of debian OS level vulnerabilities

sadpandajoe pushed a commit that referenced this pull request Mar 24, 2025
@sadpandajoe sadpandajoe added the v4.1 Label added by the release manager to track PRs to be included in the 4.1 branch label Mar 24, 2025
@gpchandran
Copy link
Contributor Author

Hi @michael-s-molina, do you have any idea when version 5.0.0 will be released? I checked Apache Superset 5.0.0 and didn't see any blockers, are we waiting on three new issues that need to be resolved.?

Hi @sadpandajoe, could you please assist with creating version 4.1.3 if version 5.0.0 is going to take longer? addressing this critical OS vulnerabilities will help everyone

@michael-s-molina
Copy link
Member

Hi @michael-s-molina, do you have any idea when version 5.0.0 will be released? I checked Apache Superset 5.0.0 and didn't see any blockers, are we waiting on three new issues that need to be resolved.?

No ETA as we depend on testing and bug fixes from the community. I added one blocker that we're currently working on.

@gpchandran
Copy link
Contributor Author

Hi @michael-s-molina, do you have any idea when version 5.0.0 will be released? I checked Apache Superset 5.0.0 and didn't see any blockers, are we waiting on three new issues that need to be resolved.?

No ETA as we depend on testing and bug fixes from the community. I added one blocker that we're currently working on.

Thanks for your response @michael-s-molina
Hi @sadpandajoe @michael-s-molina - sorry to bother, would you please help create 4.1.3, lot of OS level critical vulnerabilities will be resolved with this base python image upgrade

@mistercrunch mistercrunch added 🍒 4.1.3 Cherry-picked to 4.1.3 🍒 5.0.0 Cherry-picked to 5.0.0 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels labels Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS v4.1 Label added by the release manager to track PRs to be included in the 4.1 branch v5.0 Label added by the release manager to track PRs to be included in the 5.0 branch 🍒 4.1.3 Cherry-picked to 4.1.3 🍒 4.1.4 🍒 5.0.0 Cherry-picked to 5.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants