Skip to content

chore(deps): update BOM, parent POM, nixpkgs and CLI scanner to 1.30.1 - #175

Closed
tembleking wants to merge 1 commit into
mainfrom
chore/deps-bc-cli-1.30.1
Closed

tembleking wants to merge 1 commit into
mainfrom
chore/deps-bc-cli-1.30.1

Conversation

@tembleking

Copy link
Copy Markdown
Member

The plugin ships Bouncy Castle transitively through credentials → bouncycastle-api, so the 1.84 copy landed on every controller that installs it. Bumping the BOM pulls BC 1.85.2, which fixes a Name Constraints bypass (critical) and an ASN.1 nesting-depth guard reset (high).

This also drops IaCScanningBuilder#doCheckCredentialsId. No form field is bound to it (the UI uses engineCredentialsId), but it was still reachable by URL and looked up credentials as SYSTEM without a permission check, letting any user with Overall/Read probe which credential IDs exist.

The remaining Spring and jenkins-core alerts come from core (provided scope). The plugin doesn't ship them; they get fixed by upgrading Jenkins itself.

Bumps bouncycastle-api to pull Bouncy Castle 1.85.2, fixing a Name
Constraints bypass (critical) and an ASN.1 nesting-depth guard reset
(high). The plugin ships BC transitively via credentials, so it lands
on every controller that installs it.

Also removes IaCScanningBuilder#doCheckCredentialsId. No form field is
bound to it (the UI uses engineCredentialsId), but it was still
reachable by URL and looked credentials up as SYSTEM without a
permission check, letting any user with Overall/Read probe which
credential IDs exist.
@mateobur

Copy link
Copy Markdown
Collaborator

The version bumps look clean and consistent across code, README, tests, and fixtures. However, this deps PR also drops the doCheckCredentialsId form validation and its imports, which seems out of scope. Could you confirm that removal is intentional, or split it into its own change?

@tembleking

Copy link
Copy Markdown
Member Author

Yes, it's intentional. No form field binds to doCheckCredentialsId (the UI uses engineCredentialsId), but the endpoint was still reachable by URL and looked up credentials as SYSTEM with no permission check, so any user with Overall/Read could probe which credential IDs exist. It's a small, self-contained removal, so I'd rather ship it with this maintenance round. The PR description covers it too.

@tembleking tembleking closed this Oct 14, 2026
auto-merge was automatically disabled October 14, 2026 11:51

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants