Exporting CVE Data from the CIQ Portal

Stephen Simpson
Senior Customer Support Engineer

Introduction

The CIQ Security Advisories Portal is CIQ's public lookup for CVEs and security advisories across CIQ products, such as RLC Pro LTS, FIPS, and CIQ Bridge. For each CVE it shows the severity, whether it is fixed for each product, the advisory that fixed it, and the fixed package version.

The same data is available as JSON from the public CIQ Portal CVE API, with no account or credentials needed. The ciq-cve.py script uses that API to check and export CVE data from the command line.

Problem

You need to confirm whether a list of CVEs is fixed for your CIQ product, or export CVE and advisory data for a report, a vulnerability scanner review, or a CI pipeline.

Resolution

Download the script

Download ciq-cve.py, or fetch it from a terminal. It needs Python 3.6 or later and no extra packages.

curl -O https://kb.ciq.com/scripts/ciq-cve.py
chmod +x ciq-cve.py
./ciq-cve.py products

products lists the product keys, such as lts-9.2 or fips-9.2-compliant, that the other commands take with -p.

Check whether CVEs are fixed

$ ./ciq-cve.py check CVE-2024-6387 CVE-2023-48795 -p lts-9.2
CVE_ID          PRODUCT  STATUS  ADVISORY_ID                       FIXED_IN
CVE-2024-6387   lts-9.2  fixed   CIQSA-2026:1160                   openssh-8.7p1-38.el9_2.92ciq_lts.0.1
CVE-2023-48795  lts-9.2  fixed   CIQSA-2026:0451; CIQSA-2026:0470  libssh-0.10.4-11.el9_2.92ciq_lts; openssh-8.7p1-38.el9_2.92ciq_lts.1.0.2

FIXED_IN is the package version that carries the fix. Update to that version or later.

STATUS is one of fixed, known_not_affected, known_affected, under_investigation, no statement, or not found. no statement means CIQ has published nothing for that product, which is not the same as not affected. not found means the CVE isn't in CIQ's CVE data for any product.

To check a list of CVEs, such as from a scanner report, put one per line in a file:

./ciq-cve.py check -p lts-9.2 -o csv - < cves.txt > cve-status.csv

Use JSON output with jq to filter the results, for example to list only the CVEs that are not fixed:

./ciq-cve.py check -p lts-9.2 -o json - < cves.txt | jq -r '.[] | select(.status != "fixed") | "\(.cve_id) \(.status)"'

check exits 0 only if every CVE is fixed or known_not_affected, so it can also gate a pipeline. Without -p it only checks the products that have a statement for the CVE, so pass -p with the products you run to also fail on a missing statement.

Export CVEs and advisories

# Critical and high CVEs for a product since a date
./ciq-cve.py cves -p lts-9.2 --severity critical,high --since 2026-01-01 -o csv > lts-9.2-cves.csv

# All advisories for a product
./ciq-cve.py advisories -p lts-9.2 -o csv > lts-9.2-advisories.csv

# Full detail for one CVE or advisory
./ciq-cve.py cve CVE-2024-6387 -a
./ciq-cve.py advisory CIQSA-2026:1160

Output can be a table (the default), CSV, JSON, or YAML with -o. Run any command with -h for all options. The script honors HTTPS_PROXY and NO_PROXY; the proxy URL must use http://.

Notes

To build your own integration instead of using the script, see the API documentation.

CIQ Security Advisories Portal
CIQ CVE Remediation - Frequently Asked Questions