Running with gitlab-runner 13.8.0 (775dd39d)  on global-shared-gitlab-runner-89dbd4db8-mnp6b RKzCU9YR section_start:1617909323:resolve_secrets Resolving secrets section_end:1617909323:resolve_secrets section_start:1617909323:prepare_executor Preparing the "kubernetes" executor Using Kubernetes namespace: gitlab-runner WARNING: Pulling GitLab Runner helper image from Docker Hub. Helper image is migrating to registry.gitlab.com, for more information see https://docs.gitlab.com/runner/configuration/advanced-configuration.html#migrating-helper-image-to-registrygitlabcom Using Kubernetes executor with image ${GITLAB_INTERNAL_REGISTRY}/ironbank-tools/ironbank-pipeline/ib-pipeline-image:0.1 ... section_end:1617909323:prepare_executor section_start:1617909323:prepare_script Preparing environment Waiting for pod gitlab-runner/runner-rkzcu9yr-project-5680-concurrent-02smr7 to be running, status is Pending Running on runner-rkzcu9yr-project-5680-concurrent-02smr7 via global-shared-gitlab-runner-89dbd4db8-mnp6b... section_end:1617909326:prepare_script section_start:1617909326:get_sources Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in /builds/dsop/opensource/jupyter/jupyterhub-configurable-http-proxy/.git/ Created fresh repository. Checking out 06b21df5 as riveraj-development-patch-82625... Skipping Git submodules setup section_end:1617909327:get_sources section_start:1617909327:download_artifacts Downloading artifacts Downloading artifacts for hardening_manifest (2651985)... Downloading artifacts from coordinator... ok  id=2651985 responseStatus=200 OK token=ThGPihNQ Downloading artifacts for load scripts (2651983)... Downloading artifacts from coordinator... ok  id=2651983 responseStatus=200 OK token=EWodcw4k Downloading artifacts for wl compare lint (2651986)... Downloading artifacts from coordinator... ok  id=2651986 responseStatus=200 OK token=kbzy-Sqo section_end:1617909327:download_artifacts section_start:1617909327:step_script Executing "step_script" stage of the job script $ mkdir -p "${ARTIFACT_DIR}" $ set +e $ python3 "${PIPELINE_REPO_DIR}/stages/vat-finding-compare/vat_findings.py" api set length: 137 db set length: 135 Findings are NOT the same! There are CVEs from the api that are not returned by the query There are CVEs from the query that are not returned by the api Please run the development branch for this project before validating query/api data Findings from api not in direct query ('CVE-2021-23840', 'twistlock_cve', 'Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).', 'openssl-1.1.1g-15.el8_3', None) ('CVE-2020-13776', 'twistlock_cve', 'systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.', 'systemd-239-41.el8_3.1', None) ('CVE-2021-23840', 'anchore_cve', 'openssl-1.1.1g-15.el8_3\nhttps://access.redhat.com/security/cve/CVE-2021-23840', 'openssl-1.1.1g-15.el8_3', None) ('CVE-2020-13776', 'anchore_cve', 'systemd-libs-239-41.el8_3.1\nhttps://access.redhat.com/security/cve/CVE-2020-13776', 'systemd-libs-239-41.el8_3.1', None) ('CVE-2020-13776', 'anchore_cve', 'systemd-pam-239-41.el8_3.1\nhttps://access.redhat.com/security/cve/CVE-2020-13776', 'systemd-pam-239-41.el8_3.1', None) ('CVE-2021-23841', 'anchore_cve', 'openssl-1.1.1g-15.el8_3\nhttps://access.redhat.com/security/cve/CVE-2021-23841', 'openssl-1.1.1g-15.el8_3', None) ('CVE-2020-13776', 'anchore_cve', 'systemd-239-41.el8_3.1\nhttps://access.redhat.com/security/cve/CVE-2020-13776', 'systemd-239-41.el8_3.1', None) ('CVE-2021-23841', 'twistlock_cve', 'The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to 1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).', 'openssl-1.1.1g-15.el8_3', None) Findings from direct query not in api ('CVE-2020-13776', 'anchore_cve', 'systemd-pam-239-41.el8_3.2\nhttps://access.redhat.com/security/cve/CVE-2020-13776', 'systemd-pam-239-41.el8_3.2', None) ('41cb7cdf04850e33a11f80c42bf660b3', 'anchore_comp', "Dockerfile directive 'HEALTHCHECK' not found, matching condition 'not_exists' check\n Gate: dockerfile\n Trigger: instruction\n Policy ID: DoDDockerfileChecks", None, None) ('cbff271f45d32e78dcc1979dbca9c14d', 'anchore_comp', 'User root found as effective user, which is explicity not allowed\n Gate: dockerfile\n Trigger: effective_user\n Policy ID: DoDEffectiveUserChecks', None, None) ('CVE-2020-13776', 'twistlock_cve', 'systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.', 'systemd-239-41.el8_3.2', None) ('CVE-2020-13776', 'anchore_cve', 'systemd-libs-239-41.el8_3.2\nhttps://access.redhat.com/security/cve/CVE-2020-13776', 'systemd-libs-239-41.el8_3.2', None) ('CVE-2020-13776', 'anchore_cve', 'systemd-239-41.el8_3.2\nhttps://access.redhat.com/security/cve/CVE-2020-13776', 'systemd-239-41.el8_3.2', None) section_end:1617909328:step_script section_start:1617909328:upload_artifacts_on_failure Uploading artifacts for failed job Uploading artifacts... ci-artifacts/compare/: found 2 matching files and directories Uploading artifacts as "archive" to coordinator... ok id=2652170 responseStatus=201 Created token=z9dh1Yx3 section_end:1617909329:upload_artifacts_on_failure section_start:1617909329:cleanup_file_variables Cleaning up file based variables section_end:1617909329:cleanup_file_variables ERROR: Job failed: command terminated with exit code 4