Skip to main content
Skip table of contents

EF CX Component Vulnerability Report 2.0

This is a Vulnerability report of the Components of EFCX scanned with the trivy and published on 19-07-2024

Component

Engine

Low

Medium

High

Critical

Report

360-connector

Trivy

0

0

0

0

360-connector_trivy_report.txt

agent-manager

Trivy

0

0

0

0

agent-manager.txt

bot-framework

Trivy

0

0

0

0

bot-framework_trivy_report.txt

customer-channel-manager

Trivy

0

0

0

0

ccm_trivy_report.txt

cim-backend

Trivy

0

0

0

0

cim-backend.txt

conversation-controller

Trivy

0

0

0

0

conversation-controller_trivy_report.txt

conversation-manager

Trivy

0

0

0

0

conversation-manager_trivy_report.txt

customer-widget

Not Fixed (ambiguous results found in pervious scan)

Trivy

0

0

0

0

NOT FIXED YET

facebook-connector

Trivy

0

0

0

0

facebook-connector_trivy_report.txt

file-engine

Trivy

0

0

0

0

file-engine.txt

instagram-connector

Trivy

0

0

0

0

instagram-connector_trivy_report.txt

license-mangement

Trivy

0

0

0

0

license-manager_trivy_report.txt

realtime-reports-manager

Trivy

0

0

0

0

realtime-reporting-manager_trivy_report.txt

media-routing-engine

Trivy

0

0

0

0

media-routing-engine_trivy_report.txt

campaign-manager

Trivy

0

0

0

0

campaign-manager_trivy_report.txt

hc_smpp_connector

Trivy

0

0

0

0

hc_smpp-connector_trivy_report.txt

state-events-logger

Trivy

0

0

0

0

state-events-logger_trivy_report.txt

team-announcement

Trivy

0

0

0

0

team-announcement.txt

telegram-connector

Trivy

0

0

0

0

telegram-connector_trivy_report.txt

twilio-connector

Trivy

0

0

0

0

twilio-connector_trivy_report.txt

unified-admin

Trivy

0

0

0

0

unified-admin.txt

unified-agent

No node packages were found vulnerable in the report

Trivy

8

23

48

7

unified-agent_4.4-24-04-2024-Trivy.txt

viber-connector

Trivy

0

0

0

0

viber-connector_trivy_report.txt

web-channel-manager

Trivy

0

0

0

0

web-channel-manager.txt

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.