BugZero | ServiceNow BugID PRB1496490 - cmdb_ci_ip_address with "null" IP is not filtered ...

ServiceNow - Defect ID: PRB1496490

cmdb_ci_ip_address with "null" IP is not filtered out properly causing Azure Database pattern to fail

ServiceNow - Defect ID: PRB1496490

cmdb_ci_ip_address with "null" IP is not filtered out properly causing Azure Database pattern to fail

Last updated on November 2nd, 2024

BugZero Risk Score
5.8 Medium

Overall: 5.8

Severity: 6.4

Community: 3.7

Lifecycle: 8.2

What is the BugZero Risk Score?

ServiceNow Integration

Learn more about where this data comes from

ServiceNow Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Priority: Sev3
Article Views: 613
Affected Component: Cloud Management

Description

Workaround

Open "Azure DataBase" identification section, modify step: Keep only IPs with ip_address, add condition: $cmdb_ci_ip_address[].ip_address Not Equals "null" Save and publish the pattern.

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Affected versions:San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Fixed versions: No known fixed versions

Top ServiceNow Defects

9.4Defect ID: PRB1954123
Instance access issues due to Mutual TLS (mTLS) enablement on Zurich instances
8.5Defect ID: PRB1871576
Data visualization can be accessed by anyone with URL to visualization designer
8.5Defect ID: PRB1611377
CMDB Baseline creation job causing app node out of memory when a CI has a huge number of records referencing it
8.5Defect ID: PRB1788540
AWS Events Driven discovery is overloading Default Semaphores.
8.5Defect ID: PRB1928008
Upgrade to Yokohama releases can hang for Haraka enabled instance because of contention on kagami query registrar

Ready to prevent the next vendor outage?

Get a demo

ServiceNow Integration

Learn more about where this data comes from

ServiceNow Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

ServiceNow - Defect ID: PRB1496490

cmdb_ci_ip_address with "null" IP is not filtered out properly causing Azure Database pattern to fail

ServiceNow - Defect ID: PRB1496490

cmdb_ci_ip_address with "null" IP is not filtered out properly causing Azure Database pattern to fail

Last updated on November 2nd, 2024

BugZero Risk Score5.8 Medium

Bug Details

Workaround

Related Problem

Links

Top ServiceNow Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
5.8 Medium