Forum Discussion

Frank_ten_Wolde's avatar
Frank_ten_Wolde
Icon for Altostratus rankAltostratus
Jul 04, 2025
Solved

/config/ssl/ssl.crt/f5-ca-bundle.crt obsolete certificate

I noticed that the f5-ca-bundle.crt file contains an obsolete (root) certificate. At least up to (and including) TMOS 17.5.1.

This causes a failure when trying to update the ca-bundle.crt file using the Configuration Utility (System  ››  Certificate Management : Traffic Certificate Management : Bundle Manager List) in /var/log/ltm:

notice keymgmtd[8795]: 01a40000:5: BundleMgr /Common/ca-bundle importing from all sources.
notice keymgmtd[8795]: 01a40000:5: Download failed: https://cdn.f5.com/product/ca-bundle/blended-bundle.crt - Peer certificate cannot be authenticated with given CA certificates
notice keymgmtd[8795]: 01a40000:5: BundleMgr /Common/ca-bundle import aborted. No change to ca-bundle /Common/ca-bundle.crt

The server certificate of cdn.f5.com requires a new root CA in f5-ca-bundle.crt (noticeably: "Subject: C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46").

This was reported to F5 TAC, and will be fixed in a future release (as promised), but F5 TAC is unable to share a BugID with me.

Work around is to add (or replace?) the new certificate to f5-ca-bundle.crt, touch /service/mcpd/forceload, and reboot the appliance). This needs to be repeated after each upgrade as well, until F5 has fixed this issue.

# cp -ip /config/ssl/ssl.crt/f5-ca-bundle.crt /config/ssl/ssl.crt/f5-ca-bundle.crt.ORIG

# cat << EOF >> /config/ssl/ssl.crt/f5-ca-bundle.crt
-----BEGIN CERTIFICATE-----
MIIFijCCA3KgAwIBAgIQdY39i658BwD6qSWn4cetFDANBgkqhkiG9w0BAQwFADBf
MQswCQYDVQQGEwJHQjEYMBYGA1UEChMPU2VjdGlnbyBMaW1pdGVkMTYwNAYDVQQD
Ey1TZWN0aWdvIFB1YmxpYyBTZXJ2ZXIgQXV0aGVudGljYXRpb24gUm9vdCBSNDYw
HhcNMjEwMzIyMDAwMDAwWhcNNDYwMzIxMjM1OTU5WjBfMQswCQYDVQQGEwJHQjEY
MBYGA1UEChMPU2VjdGlnbyBMaW1pdGVkMTYwNAYDVQQDEy1TZWN0aWdvIFB1Ymxp
YyBTZXJ2ZXIgQXV0aGVudGljYXRpb24gUm9vdCBSNDYwggIiMA0GCSqGSIb3DQEB
AQUAA4ICDwAwggIKAoICAQCTvtU2UnXYASOgHEdCSe5jtrch/cSV1UgrJnwUUxDa
ef0rty2k1Cz66jLdScK5vQ9IPXtamFSvnl0xdE8H/FAh3aTPaE8bEmNtJZlMKpnz
SDBh+oF8HqcIStw+KxwfGExxqjWMrfhu6DtK2eWUAtaJhBOqbchPM8xQljeSM9xf
iOefVNlI8JhD1mb9nxc4Q8UBUQvX4yMPFF1bFOdLvt30yNoDN9HWOaEhUTCDsG3X
ME6WW5HwcCSrv0WBZEMNvSE6Lzzpng3LILVCJ8zab5vuZDCQOc2TZYEhMbUjUDM3
IuM47fgxMMxF/mL50V0yeUKH32rMVhlATc6qu/m1dkmU8Sf4kaWD5QazYw6A3OAS
VYCmO2a0OYctyPDQ0RTp5A1NDvZdV3LFOxxHVp3i1fuBYYzMTYCQNFu31xR13NgE
SJ/AwSiItOkcyqex8Va3e0lMWeUgFaiEAin6OJRpmkkGj80feRQXEgyDet4fsZfu
+Zd4KKTIRJLpfSYFplhym3kT2BFfrsU4YjRosoYwjviQYZ4ybPUHNs2iTG7sijbt
8uaZFURww3y8nDnAtOFr94MlI1fZEoDlSfB1D++N6xybVCi0ITz8fAr/73trdf+L
HaAZBav6+CuBQug4urv7qv094PPK306Xlynt8xhW6aWWrL3DkJiy4Pmi1KZHQ3xt
zwIDAQABo0IwQDAdBgNVHQ4EFgQUVnNYZJX5khqwEioEYnmhQBWIIUkwDgYDVR0P
AQH/BAQDAgGGMA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEMBQADggIBAC9c
mTz8Bl6MlC5w6tIyMY208FHVvArzZJ8HXtXBc2hkeqK5Duj5XYUtqDdFqij0lgVQ
YKlJfp/imTYpE0RHap1VIDzYm/EDMrraQKFz6oOht0SmDpkBm+S8f74TlH7Kph52
gDY9hAaLMyZlbcp+nv4fjFg4exqDsQ+8FxG75gbMY/qB8oFM2gsQa6H61SilzwZA
Fv97fRheORKkU55+MkIQpiGRqRxOF3yEvJ+M0ejf5lG5Nkc/kLnHvALcWxxPDkjB
JYOcCj+esQMzEhonrPcibCTRAUH4WAP+JWgiH5paPHxsnnVI84HxZmduTILA7rpX
DhjvLpr3Etiga+kFpaHpaPi8TD8SHkXoUsCjvxInebnMMTzD9joiFgOgyY9mpFui
TdaBJQbpdqQACj7LzTWb4OE4y2BThihCQRxEV+ioratF4yUQvNs+ZUH7G6aXD+u5
dHn5HrwdVw1Hr8Mvn4dGp+smWg9WY7ViYG4A++MnESLn/pmPNPW56MORcr3Ywx65
LvKRRFHQV80MNNVIIb/bE/FmJUNS0nAiNs2fxBx1IK1jcmMGDw4nztJqDby1ORrp
0XZ60Vzk50lJLVU3aPAaOpg+VBeHVOmmJ1CJeyAvP/+/oYtKR5j/K3tJPsMpRmAY
QqszKbrAKbkTidOIijlBO8n9pu0f9GBj39ItVQGL
-----END CERTIFICATE-----
EOF

# touch /services/mcpd/forceload

# reboot

 

 

 

 

 

  • Hello,

     

    Apologies that the support engineer did not share the issue number with you, it is ID1825913.  I have reached out to the support engineer in question to make sure they are clear on the processes for these issues.

     

    Cheers,

    Kyle Fox

    F5 Security Incident Response Team

2 Replies

  • Hello,

     

    Apologies that the support engineer did not share the issue number with you, it is ID1825913.  I have reached out to the support engineer in question to make sure they are clear on the processes for these issues.

     

    Cheers,

    Kyle Fox

    F5 Security Incident Response Team