Описание
Security update for coredns
This update for coredns fixes the following issues:
-
Update to version 1.12.1:
- core: Increase CNAME lookup limit from 7 to 10 (#7153)
- plugin/kubernetes: Fix handling of pods having DeletionTimestamp set
- plugin/kubernetes: Revert 'only create PTR records for endpoints with hostname defined'
- plugin/forward: added option failfast_all_unhealthy_upstreams to return servfail if all upstreams are down
- bump dependencies, fixing boo#1239294 and boo#1239728
-
Update to version 1.12.0:
- New multisocket plugin - allows CoreDNS to listen on multiple sockets
- bump deps
-
Update to version 1.11.4:
- forward plugin: new option next, to try alternate upstreams when receiving specified response codes upstreams on (functions like the external plugin alternate)
- dnssec plugin: new option to load keys from AWS Secrets Manager
- rewrite plugin: new option to revert EDNS0 option rewrites in responses
-
Update to version 1.11.3+git129.387f34d:
- fix CVE-2024-51744 (bsc#1232991) build(deps): bump github.com/golang-jwt/jwt/v4 from 4.5.0 to 4.5.1 (#6955)
- core: set cache-control max-age as integer, not float (#6764)
- Issue-6671: Fixed the order of plugins. (#6729)
root: explicit markdnssecsupport (#6753)- feat: dnssec load keys from AWS Secrets Manager (#6618)
- fuzzing: fix broken oss-fuzz build (#6880)
- Replace k8s.io/utils/strings/slices by Go stdlib slices (#6863)
- Update .go-version to 1.23.2 (#6920)
- plugin/rewrite: Add 'revert' parameter for EDNS0 options (#6893)
- Added OpenSSF Scorecard Badge (#6738)
- fix(cwd): Restored backwards compatibility of Current Workdir (#6731)
- fix: plugin/auto: call OnShutdown() for each zone at its own OnShutdown() (#6705)
- feature: log queue and buffer memory size configuration (#6591)
- plugin/bind: add zone for link-local IPv6 instead of skipping (#6547)
- only create PTR records for endpoints with hostname defined (#6898)
- fix: reverter should execute the reversion in reversed order (#6872)
- plugin/etcd: fix etcd connection leakage when reload (#6646)
- kubernetes: Add useragent (#6484)
- Update build (#6836)
- Update grpc library use (#6826)
- Bump go version from 1.21.11 to 1.21.12 (#6800)
- Upgrade antonmedv/expr to expr-lang/expr (#6814)
- hosts: add hostsfile as label for coredns_hosts_entries (#6801)
- fix TestCorefile1 panic for nil handling (#6802)
Список пакетов
SUSE Package Hub 15 SP6
openSUSE Leap 15.6
Ссылки
- E-Mail link for openSUSE-SU-2025:0131-1
- SUSE Security Ratings
- SUSE Bug 1239294
- SUSE Bug 1239728
- SUSE CVE CVE-2024-51744 page
Описание
golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.
Затронутые продукты
Ссылки
- CVE-2024-51744
- SUSE Bug 1232936