Summary
This update for vexctl fixes the following issues:
- Update to version 0.4.1+git78.f951e3a:
- CVE-2025-22868: Unexpected memory consumption during token parsing in golang.org/x/oauth2. (bsc#1239186)
- CVE-2024-45337: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto. (bsc#1234486)
- CVE-2025-27144: Go JOSE's Parsing Vulnerable to Denial of Service. (bsc#1237611)
- CVE-2025-22870: proxy bypass using IPv6 zone IDs. (bsc#1238683)
- CVE-2025-22869: Denial of Service in the Key Exchange of golang.org/x/crypto/ssh. (bsc#1239323)
- CVE-2025-30204: jwt-go allows excessive memory allocation during header parsing. (bsc#1240444)
- CVE-2025-58181: invalidated number of mechanisms can cause unbounded memory consumption. (bsc#1253802)
- CVE-2026-22772: MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services. (bsc#1256535)
- CVE-2026-24137: legacy TUF client allows for arbitrary file writes with target cache path traversal. (bsc#1257138)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.6 | vexctl | 0.4.1+git78.f951e3a-150000.1.11.1 |
Vulnerabilities 9
-
Critical 9.1CVE-2024-45337 Public exploit
Misuse of connection.serverAuthenticate may cause authorization bypass in golang.org/x/crypto
Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function do…
-
High 7.5
Unexpected memory consumption during token parsing in golang.org/x/oauth2
An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.
-
High 7.5
Potential denial of service in golang.org/x/crypto
SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.
-
High 7.5
jwt-go allows excessive memory allocation during header parsing
golang-jwt is a Go implementation of JSON Web Tokens. Starting in version 3.2.0 and prior to versions 5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on periods. As a result, in t…
-
Medium 6.6
Go JOSE's Parsing Vulnerable to Denial of Service
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to ve…
-
Medium 5.8
Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass
Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbi…
-
Medium 5.8
sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base direc…
-
Medium 5.3
Unbounded memory consumption in golang.org/x/crypto/ssh
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
-
Medium 4.4CVE-2025-22870 Public exploit
HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net
Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be prox…
References
-
report
https://bugzilla.suse.com/1234486
-
report
https://bugzilla.suse.com/1237611
-
report
https://bugzilla.suse.com/1238683
-
report
https://bugzilla.suse.com/1239186
-
report
https://bugzilla.suse.com/1239323
-
report
https://bugzilla.suse.com/1240444
-
report
https://bugzilla.suse.com/1253802
-
report
https://bugzilla.suse.com/1256535
-
report
https://bugzilla.suse.com/1257138
-
web
https://www.suse.com/security/cve/CVE-2024-45337
-
web
https://www.suse.com/security/cve/CVE-2025-22868
-
web
https://www.suse.com/security/cve/CVE-2025-22869
-
web
https://www.suse.com/security/cve/CVE-2025-22870
-
web
https://www.suse.com/security/cve/CVE-2025-27144
-
web
https://www.suse.com/security/cve/CVE-2025-30204
-
web
https://www.suse.com/security/cve/CVE-2025-58181
-
web
https://www.suse.com/security/cve/CVE-2026-22772
-
web
https://www.suse.com/security/cve/CVE-2026-24137