nginx-prometheus-exporter (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation5 Commits1 Checks14 Files changed

Conversation

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

[ Show hidden characters]({{ revealButtonHref }})

[ dependabot[bot] ](/apps/dependabot)

Bumps the go_modules group with 1 update in the / directory: golang.org/x/crypto.

Updates golang.org/x/crypto from 0.28.0 to 0.31.0

Commits

b4f1988 ssh: make the public key cache a 1-entry FIFO cache
7042ebc openpgp/clearsign: just use rand.Reader in tests
3e90321 go.mod: update golang.org/x dependencies
8c4e668 x509roots/fallback: update bundle
6018723 go.mod: update golang.org/x dependencies
71ed71b README: don't recommend go get
750a45f sha3: add MarshalBinary, AppendBinary, and UnmarshalBinary
36b1725 sha3: avoid trailing permutation
80ea76e sha3: fix padding for long cSHAKE parameters
c17aa50 sha3: avoid buffer copy
Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the go_modules group with 1 update in the / directory: golang.org/x/crypto.

Updates golang.org/x/crypto from 0.28.0 to 0.31.0

Commits

updated-dependencies:

dependency-name: golang.org/x/crypto dependency-type: indirect dependency-group: go_modules ...

Signed-off-by: dependabot[bot] support@github.com

jjngx deleted the dependabot/go_modules/go_modules-5a9c29dde4 branch

December 16, 2024 10:19

@ns-rtorre Nginx-prometheus-exporter code is not affected by this CVE:

➜ nginx-prometheus-exporter git:(main) ✗ govulncheck -show verbose ./... Scanning your code and 251 packages across 26 dependent modules for known vulnerabilities...

Fetching vulnerabilities from the database...

Checking the code against the vulnerabilities...

=== Symbol Results ===

No vulnerabilities found.

=== Package Results ===

No other vulnerabilities found.

=== Module Results ===

Vulnerability #1: GO-2024-3333 Non-linear parsing of case-insensitive content in golang.org/x/net/html More info: https://pkg.go.dev/vuln/GO-2024-3333 Module: golang.org/x/net Found in: golang.org/x/net@v0.32.0 Fixed in: golang.org/x/net@v0.33.0

Your code is affected by 0 vulnerabilities. This scan also found 0 vulnerabilities in packages you import and 1 vulnerability in modules you require, but your code doesn't appear to call these vulnerabilities.

@ns-rtorre and the latest tagged version v1.4.0 wasn't affected either:

➜ nginx-prometheus-exporter git:(main) ✗ git co -b test-140 v1.4.0 Switched to a new branch 'test-140' ➜ nginx-prometheus-exporter git:(test-140) ✗ git lg ➜ nginx-prometheus-exporter git:(test-140) ✗ govulncheck -show verbose ./... Scanning your code and 251 packages across 26 dependent modules for known vulnerabilities...

Fetching vulnerabilities from the database...

Checking the code against the vulnerabilities...

=== Symbol Results ===

No vulnerabilities found.

=== Package Results ===

No other vulnerabilities found.

=== Module Results ===

Vulnerability #2: GO-2024-3321 Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto More info: https://pkg.go.dev/vuln/GO-2024-3321 Module: golang.org/x/crypto Found in: golang.org/x/crypto@v0.28.0 Fixed in: golang.org/x/crypto@v0.31.0

Your code is affected by 0 vulnerabilities. This scan also found 0 vulnerabilities in packages you import and 2 vulnerabilities in modules you require, but your code doesn't appear to call these vulnerabilities.

Thanks, I also noticed that the vulnerable function ServerConfig.PublicKeyCallback is not called. Only trouble is that the vulnerable dep crypto 0.28.0 shows up in some bin scans.

Yes, that's the nature of various CVEs scanners.