fix(deps): update module github.com/cert-manager/cert-manager to v1.15.4 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/cert-manager/cert-manager	v1.13.3 -> v1.15.4

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

GHSA-r4pg-vg54-wxx4

Impact

cert-manager packages which call the standard library pem.Decode() function can take a long time to process specially crafted invalid PEM data.

If an attacker is able to modify PEM data which cert-manager reads (e.g. in a Secret resource), they may be able to use large amounts of CPU in the cert-manager controller pod to effectively create a denial-of-service (DoS) vector for cert-manager in the cluster.

Secrets are limited in size to 1MiB, which reduces the impact of this issue; it was discovered through an ~856kB fuzz test input which causes pem.Decode to take roughly 750ms to reject the input on an M2 Max Macbook Pro. By way of comparison, a valid PEM-encoded 4096-bit RSA key takes roughly 70µs to parse on the same machine.

Given the required size of PEM data needed to present a realistic DoS vector, an attacker would need to create or insert many different large sized resources in the cluster, and so the best secondary defense is to ensure that sensible limits are placed via RBAC.

This issue affects all versions of cert-manager to have been released since at least v0.1.0 (since pem.Decode is core functionality for cert-manager). All supported releases are patched.

Patches

The fixed versions are v1.16.2, v1.15.4 and v1.12.14.

• master branch: https://github.com/cert-manager/cert-manager/pull/7400
• release-1.16 branch: https://github.com/cert-manager/cert-manager/pull/7401
• release-1.15 branch: https://github.com/cert-manager/cert-manager/pull/7402
• release-1.12 branch: https://github.com/cert-manager/cert-manager/pull/7403

Workarounds

Ensure that RBAC is scoped correctly in your cluster. If a user is able to modify resources containing PEM data to be able to exploit this, it's like that those permissions are a bigger security threat than this issue - especially for Secret resources.

References

• Upstream issue: https://github.com/golang/go/issues/50116
• Similar issue: https://github.com/sigstore/sigstore/issues/198
• Google OSSFuzz: https://issues.oss-fuzz.com/issues/376728466

---

cert-manager ha a potential slowdown / DoS when parsing specially crafted PEM inputs

CVE-2024-12401 / GHSA-r4pg-vg54-wxx4 / GO-2024-3282

More information

Details

Impact

cert-manager packages which call the standard library pem.Decode() function can take a long time to process specially crafted invalid PEM data.

If an attacker is able to modify PEM data which cert-manager reads (e.g. in a Secret resource), they may be able to use large amounts of CPU in the cert-manager controller pod to effectively create a denial-of-service (DoS) vector for cert-manager in the cluster.

Secrets are limited in size to 1MiB, which reduces the impact of this issue; it was discovered through an ~856kB fuzz test input which causes pem.Decode to take roughly 750ms to reject the input on an M2 Max Macbook Pro. By way of comparison, a valid PEM-encoded 4096-bit RSA key takes roughly 70µs to parse on the same machine.

Given the required size of PEM data needed to present a realistic DoS vector, an attacker would need to create or insert many different large sized resources in the cluster, and so the best secondary defense is to ensure that sensible limits are placed via RBAC.

This issue affects all versions of cert-manager to have been released since at least v0.1.0 (since pem.Decode is core functionality for cert-manager). All supported releases are patched.

Patches

The fixed versions are v1.16.2, v1.15.4 and v1.12.14.

• master branch: https://github.com/cert-manager/cert-manager/pull/7400
• release-1.16 branch: https://github.com/cert-manager/cert-manager/pull/7401
• release-1.15 branch: https://github.com/cert-manager/cert-manager/pull/7402
• release-1.12 branch: https://github.com/cert-manager/cert-manager/pull/7403

Workarounds

Ensure that RBAC is scoped correctly in your cluster. If a user is able to modify resources containing PEM data to be able to exploit this, it's like that those permissions are a bigger security threat than this issue - especially for Secret resources.

References

• Upstream issue: https://github.com/golang/go/issues/50116
• Similar issue: https://github.com/sigstore/sigstore/issues/198
• Google OSSFuzz: https://issues.oss-fuzz.com/issues/376728466

Severity

• CVSS Score: Unknown
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/cert-manager/cert-manager/security/advisories/GHSA-r4pg-vg54-wxx4
• https://github.com/golang/go/issues/50116
• https://github.com/cert-manager/cert-manager/pull/7400
• https://github.com/cert-manager/cert-manager/pull/7401
• https://github.com/cert-manager/cert-manager/pull/7402
• https://github.com/cert-manager/cert-manager/pull/7403
• https://github.com/cert-manager/cert-manager
• https://go.dev/issue/50116
• https://pkg.go.dev/vuln/GO-2024-3282

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Potential slowdown / DoS when parsing specially crafted PEM inputs in github.com/cert-manager/cert-manager

CVE-2024-12401 / GHSA-r4pg-vg54-wxx4 / GO-2024-3282

More information

Details

Potential slowdown / DoS when parsing specially crafted PEM inputs in github.com/cert-manager/cert-manager

Severity

Unknown

References

• https://github.com/cert-manager/cert-manager/security/advisories/GHSA-r4pg-vg54-wxx4
• https://github.com/cert-manager/cert-manager/commit/3a4c9eb55e2e43570679840bbe3217869fbc8efc
• https://github.com/cert-manager/cert-manager/commit/f22f78c8c0a64d718e203b326bc844c488ad7850
• https://github.com/cert-manager/cert-manager/pull/7400
• https://github.com/cert-manager/cert-manager/pull/7401
• https://github.com/cert-manager/cert-manager/pull/7402
• https://github.com/cert-manager/cert-manager/pull/7403
• https://go.dev/issue/50116

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

---

Release Notes

cert-manager/cert-manager (github.com/cert-manager/cert-manager)

v1.15.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This patch release of cert-manager 1.15 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression

• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7261, @​cert-manager-bot)
• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7402, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.22.9 (#​7424, @​SgtCoDFish)
• Upgrade Go to 1.22.8, the latest available patch release (#​7406, @​SgtCoDFish)

v1.15.3

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.2

Bug or Regression

• BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7232, @​cert-manager-bot)

v1.15.2

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.1

Bug or Regression

• BUGFIX route53: explicitly set the aws-global STS region which is now required by the github.com/aws/aws-sdk-go-v2 library. (#​7189, @cert-manager-bot)
• Bump grpc-go to fix GHSA-xr7q-jx4m-x55m (#​7167, @SgtCoDFish)
• Fix Azure DNS causing panics whenever authentication error happens (#​7188, @cert-manager-bot)
• Fix incorrect value and indentation of endpointAdditionalProperties in the PodMonitor template of the Helm chart (#​7191, @inteon)
• Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of HTTPRoute resources (#​7186, @cert-manager-bot)
• Upgrade golang from 1.22.3 to 1.22.5 (#​7165, @github-actions)

v1.15.1

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.0

Bug or Regression

• BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7111, @​inteon)

Other (Cleanup or Flake)

• Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#​7092, @​ThatsMrTalbot)
• Bump the go-retryablehttp dependency to fix CVE-2024-6104 (#​7130, @​SgtCoDFish)

v1.15.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

cert-manager 1.15 promotes several features to beta, including GatewayAPI support (ExperimentalGatewayAPISupport), the ability to provide a subject in the Certificate that will be used literally in the CertificateSigningRequest (LiteralCertificateSubject) and the outputting of additional certificate formats (AdditionalCertificateOutputFormats).

[!NOTE]

The cmctl binary have been moved to https://github.com/cert-manager/cmctl/releases.
For the startupapicheck Job you should update references to point at quay.io/jetstack/cert-manager-startupapicheck

[!NOTE]

From this release, the Helm chart will no longer uninstall the CRDs when the chart is uninstalled. If you want the CRDs to be removed on uninstall use crds.keep=false when installing the Helm chart.

Community

Thanks again to all open-source contributors with commits in this release, including: @​Pionerd, @​SgtCoDFish, @​ThatsMrTalbot, @​andrey-dubnik, @​bwaldrep, @​eplightning, @​erikgb, @​findnature, @​gplessis, @​import-shiburin, @​inteon, @​jkroepke, @​lunarwhite, @​mangeshhambarde, @​pwhitehead-splunk & @​rodrigorfk, @​wallrj.

Thanks also to the following cert-manager maintainers for their contributions during this release: @​SgtCoDFish, @​SpectralHiss, @​ThatsMrTalbot, @​hawksight, @​inteon, @​maelvls & @​wallrj.

Equally thanks to everyone who provided feedback, helped users and raised issues on GitHub and Slack and joined our meetings!

Thanks also to the CNCF, which provides resources and support, and to the AWS open source team for being good community members and for their maintenance of the PrivateCA Issuer.

In addition, massive thanks to Venafi for contributing developer time and resources towards the continued maintenance of cert-manager projects.

Changes by Kind

Feature

• GatewayAPI support has graduated to Beta. Add the --enable-gateway-api flag to enable the integration. (#​6961, @​ThatsMrTalbot)
• Add support to specify a custom key alias in a JKS Keystore (#​6807, @​bwaldrep)
• Add the ability to communicate with Vault via mTLS when strict client certificates is enabled at Vault server side (#​6614, @​rodrigorfk)
• Added option to provide additional audiences in the service account auth section for vault (#​6718, @​andrey-dubnik)
• Venafi Issuer now sends a cert-manager HTTP User-Agent header in all Venafi Rest API requests.
  For example: cert-manager-certificaterequests-issuer-venafi/v1.15.0+(linux/amd64)+cert-manager/ef068a59008f6ed919b98a7177921ddc9e297200. (#​6865, @​wallrj)
• Add hint to validation error message to help users of external issuers more easily fix the issue if they specify a Kind but forget the Group (#​6913, @​SgtCoDFish)
• Add support for numeric OID types in LiteralSubject. Eg. "1.2.3.4=String Value" (#​6775, @​inteon)
• Promote the LiteralCertificateSubject feature to Beta. (#​7030, @​inteon)
• Promoted the AdditionalCertificateOutputFormats feature gate to Beta (enabled by default). (#​6970, @​erikgb)
• The Helm chart now allows you to supply extraObjects; a list of yaml manifests which will helm will install and uninstall with the cert-manager manifests. (#​6424, @​gplessis)
• Update the Route53 provider to support fetching credentials using AssumeRoleWithWebIdentity (#​6878, @​pwhitehead-splunk)
• Helm can now add optional hostAliases to cert-manager Pod to allow the DNS self-check to pass in custom scenarios. (#​6456, @​Pionerd)
• Added a new Ingress annotation for copying specific Ingress annotations to Certificate's secretTemplate (#​6839, @​mangeshhambarde)
• Added option to define additional token audiences for the Vault Kubernetes auth (#​6744, @​andrey-dubnik)
• Allow cert-manager.io/allow-direct-injection in annotations (#​6801, @​jkroepke)

Design

• Remove repetitive words (#​6949, @​findnature)

Bug or Regression

• BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. (#​6779, @​inteon)
• BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#​6806, @​bwaldrep)
• BUGFIX: cainjector leaderelection flag/config option defaults are missing (#​6816, @​inteon)
• BUGFIX: cert-manager issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. (#​6724, @​inteon)
• Breaking Change: Fixed unintended certificate chain is used if preferredChain is configured. (#​6755, @​import-shiburin)
• Bugfix: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#​6770, @​inteon)
• DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#​6875, @​SgtCoDFish)
• Fix backwards incompatible removal of default prometheus Service resource. (#​6699, @​inteon)
• Fix broken cainjector image value in Helm chart (#​6692, @​SgtCoDFish)
• Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#​6713, @​inteon)
• Make sure the Azure SDK error messages are stable. (#​6676, @​inteon)
• When using the literalSubject on a Certificate, the webhook validation for the common name now also points to the literalSubject. (#​6767, @​lunarwhite)
• Bump golang.org/x/net to fix CVE-2023-45288 (#​6929, @​SgtCoDFish)
• Fix ACME issuer being stuck waiting for DNS propagation when using Azure DNS with multiple instances issuing for the same FQDN (#​6351, @​eplightning)
• Fix cainjector ConfigMap not mounted in the cainjector deployment. (#​7055, @​inteon)
• Added disableAutoApproval and approveSignerNames Helm chart options. (#​7054, @​inteon)

Other (Cleanup or Flake)

• ⚠️ Possibly breaking: Helm will now keep the CRDs when you uninstall cert-manager by default to prevent accidental data loss. (#​6760, @​inteon)
• New crds.keep and crds.enabled Helm options can now be used instead of the installCRDs option. (#​6760, @​inteon)
• Bump base images (#​6840, @​inteon)
• Bump github.com/go-jose/go-jose to v3.0.3 to fix CVE-2024-28180 (#​6854, @​wallrj)
• Removed deprecated util functions that have been replaced by the slices and k8s.io/apimachinery/pkg/util packages.
  Removed deprecated CSR functions which have been replaced with other functions in the pkg/util/pki package. (#​6730, @​inteon)
• Upgrade go to 1.21.8: fixes CVE-2024-24783 (#​6823, @​inteon)
• Upgrade go to latest version 1.22.1 (#​6831, @​inteon)
• Upgrade google.golang.org/protobuf: fixing GO-2024-2611 (#​6827, @​inteon)
• cmctl and kubectl cert-manger have been moved to the https://github.com/cert-manager/cmctl repo and will be versioned separately starting with cmctl v2.0.0 (#​6663, @​inteon)
• Graduate the 'DisallowInsecureCSRUsageDefinition' feature gate to GA. (part 2) (#​6963, @​inteon)
• Remove deprecated pkg/util/pki/ParseSubjectStringToRawDERBytes function. (#​6994, @​inteon)
• Upgrade Kind to v0.23.0 and update supported node image digests (#​7020, @​github-actions[bot])
• If the --controllers flag only specifies disabled controllers, the default controllers are now enabled implicitly. (#​7054, @​inteon)
• Upgrade to Go 1.22.3, fixing GO-2024-2824. (#​6996, @​github-actions[bot])

v1.14.7

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

📜 Changes since v1.14.6

Bugfixes

• BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7113, @​cert-manager-bot)

Other (Cleanup or Flake)

• Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#​7093, @​ThatsMrTalbot)

v1.14.6

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

📜 Changes since v1.14.5

Other (Cleanup or Flake)

• Upgrade Go to 1.21.10, fixing GO-2024-2824 (GHSA-2jwv-jmq4-4j3r). (#​7008, @​inteon)
• Helm: the cainjector ConfigMap was not mounted in the cainjector deployment. (#​7053, @​cert-manager-bot)
• Updated Go to 1.21.11 bringing in security fixes for archive/zip and net/netip. (#​7076, @​ThatsMrTalbot)

v1.14.5

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.14.5 fixes a bug in the DigitalOcean DNS-01 provider which could cause incorrect DNS records to be deleted when using a domain with a CNAME. Special thanks to @​BobyMCbobs for reporting this issue and testing the fix!

It also patches CVE-2023-45288.

📜 Changes since v1.14.4

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see 1.14 release notes for more information.

Changes

Bug or Regression

• DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#​6893 , @​SgtCoDFish)
• Bump golang.org/x/net to address CVE-2023-45288 (#​6931 , @​SgtCoDFish)

v1.14.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.

⚠️ Known Issues

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations

ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

📜 Changes since v1.14.3

Bug or Regression

• Allow cert-manager.io/allow-direct-injection in annotations (#​6809, @​jetstack-bot)
• BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#​6812, @​jetstack-bot)
• BUGFIX: cainjector leaderelection flag/ config option defaults are missing (#​6819, @​jetstack-bot)

Other (Cleanup or Flake)

• Bump base images. (#​6842, @​inteon)
• Upgrade Helm: fix CVE-2024-26147 alert (#​6834, @​inteon)
• Upgrade go to 1.21.8: fixes CVE-2024-24783 (#​6825, @​jetstack-bot)
• Upgrade google.golang.org/protobuf: fixing GO-2024-2611 (#​6829, @​inteon)

v1.14.3

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.

⚠️ Known Issues

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations
• cainjector leaderelection is incorrectly disabled by default because the flag/ config option defaults are missing (https://github.com/cert-manager/cert-manager/pull/6819)

ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

📜 Changes since v1.14.2

Bug or Regression

• BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. (#​6781, @​jetstack-bot)
• BUGFIX: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#​6774, @​jetstack-bot)

v1.14.2

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.

⚠️ Known Issues

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations
• Logging-format json sometimes writes plaintext messages (see https://github.com/cert-manager/cert-manager/issues/6768). FIXED in v1.14.3

ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

📜 Changes since v1.14.1

Bug or Regression

• BUGFIX: cert-manager CA and SelfSigned issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. (#​6727, @​jetstack-bot)
• Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#​6729, @​jetstack-bot)

Other (Cleanup or Flake)

• Bump golang to 1.21.7 (#​6735, @​jetstack-bot)

v1.14.1

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.

⚠️ This version has known issues. Please install v1.14.2 instead.

⚠️ Known Issues (please install v1.14.2)

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations
• In cert-manager v1.14.0 and v1.14.1, the CA and SelfSigned issuers issue certificates with SANs set to non-critical even when the subject is empty. It incorrectly copies the critical field from the CSR.

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

ℹ️ Documentation

• Release notes
• Upgrade notes
• Installation instructions

📜 Changes since v1.14.0

Bug or Regression

• Fix broken cainjector image value in Helm chart (#​6693, @​SgtCoDFish)
• Fix bug in cmctl namespace detection which prevented it being used as a startupapicheck image in namespaces other than cert-manager. (#​6706, @​inteon)
• Fix bug in cmctl which caused cmctl experimental install to panic. (#​6706, @​inteon)

v1.14.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.

⚠️ This version has known issues. Please install v1.14.2 instead.

⚠️ Known Issues (please install v1.14.2)

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations
• In cert-manager v1.14.0 and v1.14.1, the CA and SelfSigned issuers issue certificates with SANs set to non-critical even when the subject is empty. It incorrectly copies the critical field from the CSR.
• During the release of v1.14.0, the Helm chart for this version was found to use the wrong OCI image for the cainjector Deployment,
  which caused the Helm installation to fail.
  In order to complete the release, the cert-manager team have manually updated the Helm chart for this version,
  which contains all the Helm chart fixes which are in v1.14.1.
• A bug in cmctl namespace detection prevents it being used as a startupapicheck image in namespaces other than cert-manager.
• A bug in cmctl causes cmctl experimental install to panic.

🔧 Breaking Changes

The startupapicheck job uses a new OCI image called "startupapicheck", instead of the ctl image.
If you run in an environment in which images cannot be pulled, be sure to include the new image.

The KeyUsage and BasicConstraints extensions will now be encoded as critical in the CertificateRequest's CSR blob.

🗺️ Major Themes

New X.509 Features

The cert-manager Certificate resource now allows you to configure a subset of "Other Name" SANs,
which are described in the Subject Alternative Name section of RFC 5280 (on page 37).

We specifically support any otherName type with a UTF-8 value, such as the User Principal Name or sAMAccountName.
These are useful when issuing unique certificates for authenticating with LDAP systems such as Microsoft Active Directory.
For example you can create certificates with this block in the spec:

  otherNames:
    - oid: 1.3.6.1.4.1.311.20.2.3 # UPN OID
      utf8Value: upn@domain.local

The feature is still in alpha stage and requires you to enable the OtherName feature flag in the controller and webhook components.

New CA certificate Features

You can now specify the X.509 v3 Authority Information Accessors extension,
with URLs for certificates issued by the CA issuer.

Users can now use name constraints in CA certificates.
To know more details on name constraints check out RFC section https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.10

Security

An ongoing security audit of the cert-manager code revealed some weaknesses which we have addressed in this release,
such as using more secure default settings in the HTTP servers that serve metrics, healthz and pprof endpoints.
This will help mitigate denial-of-service attacks against those important services.

All the cert-manager containers are now configured with read only root file system by default,
to prevent unexpected changes to the file system of the OCI image.

And it is now possible to configure the metrics server to use HTTPS rather than HTTP,
so that clients can verify the identity of the metrics server.

Other

The liveness probe of the cert-manager controller Pod is now enabled by default.

There is a new option .spec.keystores.pkcs12.algorithms to specify encryption and MAC algorithms for PKCS.

🤝 Community

Thanks again to all open-source contributors with commits in this release, including:

• @​ABWassim
• @​JoeNorth
• @​allenmunC1
• @​asapekia
• @​jeremycampbell
• @​jkroepke
• @​jsoref
• @​lauraseidler
• @​pevidex
• @​phillebaba
• @​snorwin
• @​tanujd11
• @​tberreis
• @​vinny

Thanks also to the following cert-manager maintainers for their contributions during this release:

• @​SgtCoDFish
• @​SpectralHiss
• @​ThatsMrTalbot
• @​hawksight
• @​inteon
• @​maelvls
• @​wallrj

Equally thanks to everyone who provided feedback, helped users and raised issues on GitHub and Slack and joined our meetings!

Thanks also to the CNCF, which provides resources and support, and to the AWS open source team for being good community members and for their maintenance of the PrivateCA Issuer.

In addition, massive thanks to Venafi for contributing developer time and resources towards the continued maintenance of cert-manager projects.

📜 Changes

Feature

• ACME challenge solver Pod for HTTP01 will get a default annotation of "cluster-autoscaler.kubernetes.io/safe-to-evict": "true". You can provide an annotation of "cluster-autoscaler.kubernetes.io/safe-to-evict": "false" in your podTemplate if you don't like this. (#​6349, @​jsoref)
• Added a clock skew detector liveness probe that will force a restart in case we detect a skew between the internal monotonic clock and the system clock of more than 5 minutes.
  Also, the controller's liveness probe is now enabled by default. (#​6328, @​inteon)
• Added a new flag (--dynamic-serving-leaf-duration) that can adjust the lifetime of the dynamic leaf certificates (#​6552, @​allenmunC1)
• Added support for otherName SANS in Certificates (#​6404, @​SpectralHiss)
• Added the option to specify the X.509 v3 Authority Information Accessors extension CA Issuers URLs for certificates issued by the CA issuer. (#​6486, @​jeremycampbell)
• Adds cert-manager's new core infrastructure initiative badge! See more details on https://www.bestpractices.dev/projects/8079 (#​6497, @​SgtCoDFish)
• All Pods are now configured with readOnlyRootFilesystem by default. (#​6453, @​wallrj)
• MAYBE BREAKING: The startupapicheck job is now handled by an entirely new container called "startupapicheck". This replaces the previous ctl container. If you run in an environment in which images cannot be pulled, be sure to include the new container. (#​6549, @​SgtCoDFish)
• New option .spec.keystores.pkcs12.algorithms to specify encryption and MAC algorithms for PKCS#​12 keystores. Fixes issues #​5957 and #​6523. (#​6548, @​snorwin)
• The ACME HTTP01 solver Pod is now configured with readOnlyRootFilesystem: true (#​6462, @​wallrj)
• Updates the AWS SDK for Go to 1.48.7 to support Amazon EKS Pod Identity (#​6519, @​JoeNorth)
• Users can now use name constraints in CA certificates. To know more details on name constraints check out RFC section https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.10 (#​6500, @​tanujd11)
• ⚠️ potentially breaking ⚠️: The KeyUsage and BasicConstraints extensions will now be encoded as critical in the CertificateRequest's CSR blob. (#​6053, @​inteon)
• Add TLS support to the metrics endpoint through either a certificate file or through dynamically issued certificates (#​6574, @​ThatsMrTalbot)
• Helm Chart: allow changing the default Deployment revisionHistoryLimit (#​6248, @​tberreis)
• Security: Limit the size of the response body read from HTTP requests by cert-manager. (#​6619, @​ThatsMrTalbot)
• Support custom spec.namespaceSelector for webhooks (#​6638, @​jkroepke)

Bug or Regression

• BUGFIX[helm]: Fix issue where webhook feature gates were only set if controller feature gates are set. (#​6380, @​asapekia)
• Controller ConfigMap is now created only if .Values.config is set. (#​6357, @​ABWassim)
• Fix runaway bug caused by multiple Certificate resources that point to the same Secret resource. (#​6406, @​inteon)
• Fix(helm): templating of required value in controller and webhook ConfigMap resources (#​6435, @​ABWassim)
• Fixed a webhook validation error message when the key algorithm was invalid. (#​6571, @​pevidex)
• Fixed error messaging when setting up vault issuer (#​6433, @​vinny)
• GHSA-vgf6-pvf4-34rq: The webhook server now returns HTTP error 413 (Content Too Large) for requests with body size >= 3MiB. This is to mitigate DoS attacks that attempt to crash the webhook process by sending large requests that exceed the available memory.
  The webhook server now returns HTTP error 400 (Bad Request) if the request contains an empty body.
  The webhook server now returns HTTP error 500 (Internal Server Error) rather than crashing, if the code panics while handling a request. (#​6498, @​inteon)
• Increase the default webhook timeout to its maximum value of 30 seconds, so that the underlying timeout error message has more chance of being returned to the end user. (#​6488, @​wallrj)
• Listeners that do not support TLS on Gateway resources will now not raise BadConfig warnings anymore (#​6347, @​lauraseidler)
• Mitigate potential Slowloris attacks by setting ReadHeaderTimeout in all http.Server instances (#​6534, @​wallrj)
• The Venafi issuer now properly resets the certificate and should no longer get stuck with WebSDK CertRequest Module Requested Certificate or `This certificate cannot be processed while it is in an error state. Fix any errors, and then

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 4 additional dependencies were updated

Details:

Package	Change
github.com/emicklei/go-restful/v3	v3.11.0 -> v3.12.0
github.com/go-jose/go-jose/v4	v4.0.1 -> v4.0.2
github.com/go-openapi/jsonreference	v0.20.2 -> v0.21.0
sigs.k8s.io/gateway-api	v0.8.0 -> v1.1.0