Skip to main content

Illumio Core What's New and Release Notes for 23.5

Resolved Issues in Release 23.5.10

Important

Illumio Core 23.5.10 is available for Illumio On-Premises customers only.

Enterprise Server

  • Traffic query was returning unexpected results (E-112418)

    This issue is fixed, and the generated SQL queries for all scenarios look as expected.

  • The service background_worker crashed on large async API responses (E-112383)

    This issue was observed for async APIs on large workload collections. This issue is resolved.

  • An error was thrown during the bulk Import of Workload labels when the labels contained double-byte characters (E-112278)

    This issue is fixed, and users can import double-byte characters.

  • The Ransomware Dashboard was displaying the same port/process multiple times (E-112055)

    This issue is fixed.

  • ERROR: cannot DROP TABLE "event_bus_changes" was triggered with pending trigger events (E-111745)

    This regression was caused by an optimization introduced to drop a temp table to avoid vacuum buildup. This issue is resolved.

  • Upgrade PostgreSQL to address CVE-2023-5869 and CVE-2023-5868 (E-111556)

    PostgreSQL was upgraded to mitigate exposure to two CVEs: CVE-2023-5868 and CVE-2023-5869. As the PCE uses PostgreSQL internally and does not offer external user access the likelihood of this exploit is low without additional access privileges. PostgreSQL was upgraded as a cautionary measure to address two CVEs.

  • Added unmanaged workloads from Explorer no longer use hostnames (E-111363)

    When unmanaged workloads were created from Illumination Plus (Explorer), the priority for the workload name was the hostname followed by the IP Address. IP Address will be considered when the hostname for a workload doesn't exist.

  • Vulnerability data was showing on the map only upon interaction (E-111087)

    Vulnerability data was shown on the Vulnerability Map only when users interacted with it. This issue is resolved.

  • The reported view was not showing if a flow was blocked (E-111058)

    The reported view did not show if a flow was blocked by a source or destination in Illumination Plus.This issue is resolved and works as expected.

  • The Traffic query against Windows outbound service objects was not working (E-111046)

    This issue is resolved and works as expected.

  • Traffic query was not showing blocked DHCPDISCOVERING flows (E-110940)

    Traffic query did not show blocked DHCPDISCOVERING flows with FlowCollection set to aggregate broadcast traffic.This is resolved and works as expected.

  • The source port/process was not showing for the selected flow (E-110514)

    This issue is resolved and works as expected.

  • Saving filter with duplicate name did not give an error (E-110132)

    No error was triggered when a filter containing a duplicate name was saved.This issue is resolved, and saving a duplicate name for a filter gives an error: "A filter with that name already exists. This will overwrite the existing filter".

  • The PCE was proposing to delete a valid rule when another rule was provisioned (E-109240)

    The resolution is to default to not consolidating the rules already existing in the ruleset.

  • IP list traffic did not appear in searches (E-108490)

    The IP list traffic was not appearing in searches due to including a list containing an FQDN in query parameters.This leads to the inclusion of region_id in the sql query that is executed in each region. However, the region_id being passed is the leader's region id. The issue happens only on a supercluster.

  • Creating a traffic report for the Default Graph resulted in an endless loop (E-108203)

    This issue is resolved and works as expected.

  • The Illumination Plus query involving a Process and a Port without traffic yielded no results (E-108060)

    However, removing the Port produced results. The services include filter should function as an OR, as the tooltip indicates, instead of an AND when specifying processes with ports.

  • Blank space in the IP address caused a query to fail (E-106290)

    When filtering by IP address in Explorer > Traffic, the query failed if a blank space appeared after an IP address in the filter criteria. This issue is resolved.

  • Mesh was re-rendering repeatedly and interactions did not work (E-105167)

    Hover and brush interactions on Mesh have nit not been working properly and images re-render repeatedly. This issue is resolved.

  • Proposed Rules - Status information was hidden (E-105098)

    The Proposed Rules status information was hidden by the Ruleset Summary page. This issue is resolved.

  • Selecting a saved filter did not return any results (E-102257)

    When loading a saved filter in Illumination Plus, the PCE did not return any results for the query. This situation occurred when users selected the Reported Policy Decision option in Illumination Plus. This issue is resolved.

PCE Platform

  • The PCE failed to initialize in FIPS mode on RHEL 8.3 or higher with Ruby 3.1.2 (E-111825)

    When operating in FIPS mode on EL 8.3 or higher, the PCE could not start on an initial install. A change in the runtime environment introduced this issue, which has now been fixed.

UI Components

  • The Merge option for Proposed rules was merging Existing rules (E-111593)

    This issue is fixed, and the UI works as expected.

VEN

  • VEN asked for a maintenance token on unsupported OSes for tampering protection (E-101470)

    When VEN tampering protection was enabled, Solaris and macOS workloads (where VEN tampering protection is not yet supported) also requested a maintenance token for CLI commands. CLI commands other than suspend would succeed if a valid maintenance token was provided, while suspend did not work even when a valid token was provided. This issue is resolved.