BugZero | F5 BugID 704555 - Core occurs if DIAMETER::persist reset is called i...

F5 - Defect ID: 704555

Core occurs if DIAMETER::persist reset is called if no persistence key is set.

F5 - Defect ID: 704555

Core occurs if DIAMETER::persist reset is called if no persistence key is set.

Last updated on July 18th, 2026

BugZero Risk Score
8.4 High

Overall: 8.4

Severity: 9.1

Community: 4.2

Lifecycle: 7.0

What is the BugZero Risk Score?

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Bug Details

Priority: 2-Critical
Status: Verified
Impact Category: Service Provider

Description

Symptoms

tmm crashes and restarts.

Impact

Traffic disrupted while tmm restarts.

Conditions

The system is configured to use a custom persistence key, but no persistence key has been set and DIAMETER::persist reset command is used.

Workaround

Avoid using DIAMETER::persist reset if a persistence key has not been set.

Fix Information

System ignores the reset command if the key has not been set

Change history

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:13.0.0, 13.0.0 hf1, 13.0.0 hf2, 13.0.0 hf3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed versions: 14.1.0, 14.0.0.5, 13.1.1.5

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: 14.1.0, 14.0.0.5, 13.1.1.5

Top F5 Defects

9.6Defect ID: 546260
TMM can crash if using the v6rd profile
9.6Defect ID: 934133
Unable to Create/delete ltm virtual server via CLI transaction when destination is not specified on the ltm virtual object
9.6Defect ID: 1154417
Profile based attack is not mitigated at hardware on L2 wire setup
9.6Defect ID: 913713
Rebooting a blade causes MCPd to core as it rejoins the cluster
9.6Defect ID: 2141125
Multicast traffic is dropped with incorrect VLAN tagging

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Ready to prevent the next vendor outage?

Get a demo

F5 - Defect ID: 704555

Core occurs if DIAMETER::persist reset is called if no persistence key is set.

F5 - Defect ID: 704555

Core occurs if DIAMETER::persist reset is called if no persistence key is set.

Last updated on July 18th, 2026

BugZero Risk Score8.4 High

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

F5 - Defect ID: 704555

Core occurs if DIAMETER::persist reset is called if no persistence key is set.

F5 - Defect ID: 704555

Core occurs if DIAMETER::persist reset is called if no persistence key is set.

Last updated on July 18th, 2026

BugZero Risk Score8.4 High

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
8.4 High

BugZero Risk Score
8.4 High