Answer a vulnerability inquiry
In this tutorial, you answer a customer who asks whether Acme Shop is affected by a vulnerability. You find the team’s assessment in the Vulnlog file and turn it into an answer, without analysing the vulnerability again. It takes about 5 minutes.
The customer writes:
Our scanner flags CVE-2024-3094, the XZ Utils backdoor, in the Acme Shop 4.3.0 container image. Are we affected?
Before you start
You don’t need the Vulnlog CLI.
-
Make sure the
grepcommand is available. Linux and macOS include it, but Windows doesn’t by default. -
Create an empty directory and save the Acme Shop Vulnlog file in it as
acme-shop.vl.yaml:acme-shop.vl.yaml
# $schema: https://vulnlog.dev/schema/vulnlog-v1.json --- schemaVersion: "1" project: organization: Acme Corp name: Acme Shop author: Acme Product Security Team contact: security@acme.example tags: - id: backend description: Java server application - id: frontend description: Web user interface - id: worker description: Python report worker - id: container description: Container image that bundles all components releases: - id: 4.2.0 published_at: 2026-03-02 purls: - purl: "pkg:maven/com.acme/acme-shop-server@4.2.0" tags: [backend] - purl: "pkg:oci/acme-shop@sha256:cf9066b0fcef66d545007bd33b5d8d59e7434e37c2a23d19a3075fdb6f0b48b9" tags: [container] - id: 4.3.0 published_at: 2026-06-15 purls: - purl: "pkg:maven/com.acme/acme-shop-server@4.3.0" tags: [backend] - purl: "pkg:oci/acme-shop@sha256:23a5bff22a95119dc4bcef9422a20038eb3c2fd355f03928b02791273ff1cc27" tags: [container] - id: 4.4.0 purls: - purl: "pkg:maven/com.acme/acme-shop-server@4.4.0" tags: [backend] - purl: "pkg:oci/acme-shop@sha256:350f97615163b67cbff8b015e60c77c2cbb954b4d9ffa9d48254e216e54899c8" tags: [container] vulnerabilities: - id: CVE-2023-32681 description: Proxy-Authorization header leak in requests releases: [4.3.0] packages: ["pkg:pypi/requests@2.28.2"] reports: - reporter: github-dependabot at: 2026-07-14 tags: - worker - container - id: CVE-2024-3094 name: XZ Utils backdoor description: Backdoor in the liblzma library of XZ Utils releases: [4.3.0] packages: ["pkg:deb/debian/xz-utils@5.4.1"] reports: - reporter: other at: 2026-07-02 source: Customer inquiry tags: [container] analysis: >- The container image is based on Debian 12, which ships xz-utils 5.4.1. The backdoor is only in the upstream releases 5.6.0 and 5.6.1. analyzed_at: 2026-07-02 verdict: not affected justification: vulnerable code not present - id: CVE-2022-42889 name: Text4Shell description: Remote code execution through string interpolation in Apache Commons Text releases: - 4.2.0 - 4.3.0 packages: ["pkg:maven/org.apache.commons/commons-text@1.9"] reports: - reporter: dependency-check at: 2026-05-20 tags: - backend - container analysis: >- Acme Shop only uses StringEscapeUtils from Commons Text. The server never calls StringSubstitutor, which performs the vulnerable interpolation. analyzed_at: 2026-05-21 verdict: not affected justification: vulnerable code not in execute path - id: CVE-2022-22965 name: Spring4Shell description: Remote code execution through data binding in Spring Framework releases: - 4.2.0 - 4.3.0 packages: ["pkg:maven/org.springframework/spring-beans@5.3.15"] reports: - reporter: trivy at: 2026-04-07 suppress: expires_at: 2027-03-31 tags: - backend - container analysis: >- Acme Shop runs as a Spring Boot executable JAR on JDK 17. The published exploit needs a WAR deployment on Apache Tomcat, but Spring advises all users to upgrade. analyzed_at: 2026-04-08 verdict: affected severity: medium disposition: will fix comment: Planned for 4.4.0 together with the Spring Boot update. - id: CVE-2021-23337 description: Command injection through the template function in lodash releases: - 4.2.0 - 4.3.0 packages: ["pkg:npm/lodash@4.17.20"] reports: - reporter: npm-audit at: 2026-03-10 suppress: {} tags: [frontend] analysis: >- The template function is only used in the admin interface, with templates that administrators write. Administrators can already change the shop configuration, so the injection gives them no additional access. The admin interface is removed in Acme Shop 5.0. analyzed_at: 2026-03-12 verdict: affected severity: low disposition: wont fix - id: CVE-2021-44228 name: Log4Shell description: Remote code execution through JNDI lookups in Apache Log4j aliases: [GHSA-jfh8-c2jp-5v3q] releases: [4.2.0] packages: ["pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1"] reports: - reporter: grype at: 2026-03-10 - reporter: other at: 2026-03-11 source: Customer support request tags: - backend - container analysis: >- The server logs the User-Agent header with log4j-core 2.14.1. A crafted header triggers a JNDI lookup and runs attacker-controlled code. analyzed_at: 2026-03-11 verdict: affected severity: critical disposition: will fix resolution: in: 4.3.0 at: 2026-06-15 note: Updated log4j-core from 2.14.1 to 2.17.1
Run every command in this tutorial from the directory that contains acme-shop.vl.yaml.
Find the entry
Search the file for the identifier the customer gave you:
grep -n "CVE-2024-3094" acme-shop.vl.yaml
56: - id: CVE-2024-3094
The entry starts on line 56. Open the file in your editor and go to that line.
A customer’s scanner sometimes uses a different identifier for the same vulnerability.
The aliases field of an entry lists the other identifiers, and a search finds them too.
For example, search for GHSA-jfh8-c2jp-5v3q, the alias of Log4Shell:
grep -n "GHSA-jfh8-c2jp-5v3q" acme-shop.vl.yaml
140: aliases: [GHSA-jfh8-c2jp-5v3q]
Read the assessment
The entry for CVE-2024-3094 reads:
- id: CVE-2024-3094
name: XZ Utils backdoor
description: Backdoor in the liblzma library of XZ Utils
releases: [4.3.0]
packages: ["pkg:deb/debian/xz-utils@5.4.1"]
reports:
- reporter: other
at: 2026-07-02
source: Customer inquiry
tags: [container]
analysis: >-
The container image is based on Debian 12, which ships xz-utils 5.4.1. The backdoor is only in the upstream releases 5.6.0
and 5.6.1.
analyzed_at: 2026-07-02
verdict: not affected
justification: vulnerable code not present
Read the fields that matter for your answer:
-
releasesis[4.3.0], the release the customer runs. -
packagesnames the affected package as a package URL (PURL), a standard way to name a package, its ecosystem, and its version in one string. Here it’s version 5.4.1 of the Debian packagexz-utils. -
tagsis[container], so the assessment is about the container image, which is what the customer scans. -
verdictisnot affected. This is the team’s answer to the customer’s question. -
justificationisvulnerable code not present. This value comes from a fixed list that VEX uses. VEX (Vulnerability Exploitability eXchange) is a standard way to tell others whether a vulnerability affects a product. -
analysisis the team’s reasoning, in words you can pass on: the image ships xz-utils 5.4.1, and the backdoor is only in 5.6.0 and 5.6.1. -
analyzed_atis the date of the analysis, 2 July 2026.
The reports field shows that the team first heard of this vulnerability through a customer inquiry on 2 July 2026.
The team analysed it the same day, so you can answer now without new work.
Write the answer
Base every statement on a field of the entry:
Thank you for your question. Acme Shop 4.3.0 isn’t affected by CVE-2024-3094. The container image is based on Debian 12, which ships xz-utils 5.4.1. The backdoor is only in the upstream releases 5.6.0 and 5.6.1, so the vulnerable code isn’t present in the image. Our security team completed this analysis on 2 July 2026.
What you’ve learned
Now you can:
-
Find an entry by its identifier or one of its aliases.
-
Check that an assessment covers the customer’s release.
-
Base an answer on the verdict, justification, and analysis of an entry.
Next steps
-
Record an inquiry about a vulnerability that has no entry yet in Triage a new scanner finding.
-
Find out how the Git history shows who recorded a verdict and when in Why your analysis lives in Git.
-
Give customers an overview of every vulnerability with Generate reports.
-
Publish OpenVEX documents, which tell your customers' tools whether a release is affected by a vulnerability. See Generate OpenVEX documents.
-
Look up every justification value in Verdicts and justifications.