Tool guideSecurity & Testing

SBOM Security Analyzer – Complete Guide to CycloneDX and SPDX SBOMs, Dependencies and CVE Matching

What an SBOM is, how CycloneDX and SPDX describe components and dependencies, how the NetTools.tech SBOM Security Analyzer parses them in your browser, matches packages to NVD CVEs by CPE, and how to read the risk score, match confidence and dependency graph.

By NetTools.tech · · 13 min read

A customer asks for the SBOM of your product, your build pipeline already emits one, or an auditor wants to know which of the 800 packages in a container image have known vulnerabilities. The SBOM answers "what is inside", but not "is any of it vulnerable", "how did that library get in" or "which version fixes it" — and reading thousands of JSON lines by hand does not scale.

The SBOM Security Analyzer reads a CycloneDX or SPDX SBOM in your browser, shows its components, suppliers, licenses and dependency tree, checks every package that can be identified reliably against NVD, and links each CVE to its full record in CVE Search. It is meant for developers, release managers and security teams who need a quick, explainable view of an SBOM without installing a scanner.

What is an SBOM?

In simple terms

A Software Bill of Materials (SBOM) is an ingredient list for software: every library, framework and package an application contains, with its version and, ideally, a unique identifier and the relationships between them. An SBOM analyzer turns that list into answers — how many dependencies there are, which are direct, which are pulled in by other packages, and which versions have publicly known vulnerabilities.

Technical background

TermWhat it isUsed by the analyzer for
CycloneDXOWASP SBOM standard in JSON or XML; components, metadata.component (the application) and a dependencies listComponents, root application, dependency edges, tools, authors, licenses
SPDXLinux Foundation / ISO standard; packages, relationships and documentDescribesPackages, the described root, relationships such as DEPENDS_ON, CONTAINS, DEPENDENCY_OF, DEV_DEPENDENCY_OF
PURLPackage URL, e.g. pkg:npm/[email protected] or pkg:maven/org.apache.logging.log4j/[email protected]: type, namespace, name, versionEcosystem, name and version for CPE lookup
CPECommon Platform Enumeration, e.g. cpe:2.3:a:openssl:openssl:1.1.1k:*:*:*:*:*:*:*; the product names NVD usesThe key for asking NVD which CVEs apply
NVDNational Vulnerability Database (NIST); CVE analysis with CPE configurations and version rangesApplicable CVEs, CVSS, CWE, KEV flag, fixed versions
Direct / transitiveA direct dependency is used by the application itself; a transitive one is reached only through another dependencyPrioritisation, risk weighting, "how it enters the application"

The crucial step is identity. NVD does not index CVEs by npm or PyPI package names; it uses CPE names chosen by its analysts, such as lodash:lodash or request_project:request. Bridging PURL to CPE is where SBOM scanners differ, and where name-only matching produces false positives (many vendors have a product called core or request).

Why use the SBOM Security Analyzer?

  • See what you ship: component count, direct versus transitive dependencies, ecosystems, unique suppliers and licenses.
  • Find known CVEs per component with severity, CVSS vector, CWE, CISA KEV flag and NVD's fixed version.
  • Understand the path: the shortest dependency chain from your application to each vulnerable package, so you know which direct dependency to upgrade.
  • Judge the SBOM itself: quality checks show components without versions, PURLs, CPEs, suppliers or licenses — gaps that make any vulnerability scan incomplete.
  • Hand results on: CSV, JSON, copy and print exports with the match confidence and source of each finding.

Who should use it?

Developers and DevOps engineers reviewing dependencies before a release, security and vulnerability-management teams triaging an SBOM received from a supplier, release managers who must deliver an SBOM to customers and want to check it first, and auditors who need a sourced, explainable list of components and CVEs.

How the SBOM Security Analyzer works

Parsing in the browser. The file (up to 25 MB, at most 20,000 components) is parsed in your browser; nothing in it is executed, fetched or resolved. Nested CycloneDX components are flattened, metadata.component (CycloneDX) or the DESCRIBES target (SPDX) becomes the root application, NOASSERTION counts as empty, and relationships to unknown components are dropped with a warning. The XML reader rejects any DOCTYPE or entity declaration (no XXE).

Dependency structure. From the edges the analyzer computes, for every component, the shortest depth from the root: depth 1 is direct, deeper is transitive. Without a root application, components that nothing depends on serve as roots. If the SBOM has no relationships at all, every component is unknown — the analyzer does not guess.

What is sent, and what is not. Before anything goes to the server, the browser marks components without a version, or without any PURL or CPE, as Unable to determine; they are never sent. For the rest, one entry per unique package (key, name, version, PURL, CPE, ecosystem) is sent to the NetTools API in batches of at most 150 entries and about 11.5 KB. The server accepts at most 5,000 unique packages per scan, two running scans per client and 40 jobs in total. A job is deleted on Clear analysis, when you load another SBOM or leave the page, 60 minutes after it finished, or on a server restart.

Matching against NVD. The NetTools server resolves each package in order, never by name alone:

  1. CPE in the SBOM with a version → NVD is asked for CVEs of exactly that CPE (exact match, or No known CVEs).
  2. Otherwise the PURL name (without npm scope or Maven group, with PyPI -/_ variants and Maven suffixes like -core stripped as alternatives) is looked up in the NVD CPE dictionary, first at the installed version, then without a version.
  3. The ecosystem helps pick the vendor: npm expects node.js in the CPE's target software, PyPI python, Maven java, NuGet .net, and so on; a PURL namespace that matches the vendor also counts. One consistent vendor at the installed version gives a strong match; several vendors, an unconfirmed ecosystem or a version missing from the dictionary give a possible match (up to three vendors are queried).
  4. NVD's CVE API is queried with cpeName for that version (rejected CVEs excluded, up to 2,000 CVEs per CPE), and NVD decides whether the version falls inside each CVE's affected range.
  5. No dictionary entry at all → Unable to determine.

Fixed versions. For each CVE the server reads NVD's CPE configurations for the matched vendor and product and takes the lowest versionEndExcluding above your version. If NVD gives none, the field says "not stated by NVD".

Pacing, caching and failures. NVD requests share the CVE Search rate limiter: 5 requests per 30 seconds without an NVD API key, 45 with one. CPE dictionary answers are cached for 24 hours, CVE lists per CPE for 6 hours. A package whose lookup fails (rate limit reached, timeout) is marked Lookup failed and the scan continues; finished packages are kept. The browser polls for new results every 1.5 seconds and merges them as they arrive.

How to use the NetTools.tech SBOM Security Analyzer

  1. Open the SBOM Security Analyzer.
  2. Load an SBOM: drop the file on the drop zone, click Select file (.json, .xml, .cdx, .spdx), click Paste SBOM, paste the content and press Analyze, or click Try an example for a small CycloneDX SBOM with real npm packages.
  3. Watch the progress steps: parsed components, dependency relationships built, then "Checking vulnerabilities: done / total packages" with the package currently being checked and an estimate of the remaining time.
  4. Use the tabs:
    • Overview — SBOM metadata, composition, risk score, charts and quality checks.
    • Components — searchable table (name, PURL, supplier, license) with filters Dependency, Ecosystem, Status (Vulnerable, No known CVEs, Cannot be checked) and Sort (Highest severity, Most CVEs, Name, Depth), 50 rows per page.
    • Vulnerabilities — one card per CVE and component, 25 per page, with a Match confidence filter (All, Exact / strong, Possible only).
    • Dependency graph — layered graph with search, Depth (1, 2, 3, 4, 6 or All levels; default 3), Only paths to vulnerable components, zoom and Fit.
  5. Click a severity card (All vulnerabilities, Critical, High, Medium, Low, Unknown (not scored)) to filter; from Overview or the graph it switches to the Vulnerabilities tab.
  6. Click a component name to open its details dialog, and View CVE or a CVE ID to open the full record in CVE Search in a new tab.
  7. Export the current view with CSV, JSON, Copy all or Print. If lookups failed, press Retry scan; when done, press Clear analysis.

Tip

If many components are "Unable to determine" because they lack PURLs or versions, regenerate the SBOM with your build tool's CycloneDX or SPDX plugin rather than a hand-written one. Identifiers are what make matching possible.

Understanding the results

Overview

ResultMeaningWhat to look for
SBOMFormat, spec version and encoding, name, author, manufacturer, creation time, generating tool, serial number or SPDX namespaceAn old creation date means the SBOM may not match what is deployed
CompositionComponents, direct and transitive dependencies, relationships, unique suppliers, licenses, ecosystems"unknown (no relationships)" means direct/transitive cannot be determined
SBOM security riskNetTools score 0–100 and rating: None found (0), Low (below 25), Medium (25–49), High (50–74), Critical (75+)A NetTools assessment, not a standard; unmatched components are not included
Risk listVulnerable components, vulnerable direct and transitive dependencies, unknown versions, missing PURL/CPE, unresolved matchesHigh "unresolved" counts mean the score understates the risk
ChartsFindings per severity, dependency composition, ten most vulnerable components (bar color = highest severity)Click a bar to filter or open the component
SBOM qualityChecks for names, versions, PURL or CPE, PURL, supplier, license, graph connectivity, plus parser warningsMissing versions and identifiers directly reduce matching

Components, vulnerabilities and details

ResultMeaningWhat to look for
Dependencydirect or transitive with depth in parentheses, or — when unknownDirect ones are under your control; transitive ones need an upgrade of the parent or an override
Match tagExact match, Strong match, Possible match, No known CVEs, Unable to determine, Lookup failedVerify every possible match: is this really the product NVD lists?
Finding cardCVE ID, severity and score, CVSS version, Known exploited tag, component, attack vector, complexity, privileges, user interaction, fixed version, vector string, CWE, dates, "Source: NVD"KEV plus a direct dependency first
NOT SCOREDNVD has no CVSS score yet; counted as Unknown, never as LowOpen the record; the CNA may have published more
Matching (dialog)Status, how the CPE was found, and why a match was impossible"NVD has no CPE for …" means NVD cannot answer for this package
NVD CPE usedThe CPE name the server queriedCheck vendor and product against the real project
How it enters the applicationShortest path from the root to the component; also Dependencies and Used by listsUpgrade the first direct dependency on the path
RemediationCurrent version, Recommended version, the CVEs it fixes, CVEs without a stated fixThe recommendation can be a major version jump; read release notes
Detected in your SBOM (CVE page)On a CVE opened from the analyzer: component, installed and fixed version, dependency, path, match confidence (up to 10 components)Tab-local; disappears with Clear analysis

Example: the built-in example SBOM

Click Try an example in the SBOM Security Analyzer. The file is a CycloneDX 1.5 JSON SBOM for an application my-app 1.0.0 from "Example Corp", generated by @cyclonedx cyclonedx-npm 1.19.0:

my-app 1.0.0
├── express 4.17.1          (direct)
│   └── lodash 4.17.20      (transitive, depth 2)
├── axios 0.21.1            (direct)
│   └── follow-redirects 1.14.7  (transitive, depth 2)
├── @babel/core 7.20.0      (direct)
│   ├── json5 2.2.1         (transitive, depth 2)
│   └── lodash 4.17.20
└── internal-lib            (direct, no version, no PURL)

Parsing. Seven components; json5 is a nested CycloneDX component and is flattened. Express also lists a dependency ghost-ref that is not in the SBOM, so the quality section warns that 1 dependency relationship referred to unknown components and was ignored. It also reports one component missing a version and one missing a PURL or CPE: internal-lib, which shows Unable to determine ("No version: a vulnerability cannot be determined without one.") and is never sent to the server.

A finding. Six packages are sent for matching. For pkg:npm/[email protected] the server finds cpe:2.3:a:lodash:lodash:4.17.20:*:*:*:*:node.js:*:* in the CPE dictionary; the target software node.js confirms the npm ecosystem, so the match is strong. The NVD record of CVE-2021-23337 as stored for the NetTools test suite reads: CVSS 3.1 7.2 High, CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, CWE-94, affected range ending before 4.17.21 — so the card shows Fixed version: 4.17.21, and the component dialog shows the path my-app 1.0.0 → express 4.17.1 → lodash 4.17.20 with Recommended version 4.17.21. Which other CVEs appear for the remaining packages depends on NVD's data at the time of the scan.

Score arithmetic. If this High finding on a transitive dependency were the only one, it would give 5 points and a score of round(100 × (1 − e^(−5/50))) = 10, rated Low. A single Critical CVE in CISA KEV on a direct dependency gives 10 × 1.5 + 5 = 20 points and a score of 33, rated Medium.

Common use cases

  • Pre-release check: upgrade direct dependencies with Critical, High or KEV findings.
  • Supplier SBOM review: check a delivered SBOM for missing identifiers and known CVEs.
  • Explaining a finding: the dependency path shows which top-level package brings in a vulnerable library.
  • Ticketing: export the vulnerability table as CSV and link each ticket to the CVE record.

Troubleshooting

The file is rejected as unsupported

SPDX tag-value, RDF/XML and 3.0 are not read; export SPDX 2.2/2.3 JSON or CycloneDX instead. CycloneDX needs version 1.2–1.6: a specVersion in JSON, the namespace http://cyclonedx.org/schema/bom/1.x in XML. XML with a DOCTYPE or entity declaration is refused to prevent entity attacks.

Most npm packages are "Unable to determine"

The reason in the component dialog tells you which case applies. "NVD has no CPE for …" means NVD has never assigned a CPE to that package, which is common for small npm packages; NVD cannot answer for it, and NetTools does not fall back to name matching. Check such packages with your ecosystem's own advisory tooling.

Direct and transitive are all "unknown"

The SBOM has no dependencies (CycloneDX) or dependency relationships (SPDX). Many generators have an option to include the dependency tree.

The scan takes many minutes or shows "Lookup failed"

Without an NVD API key on the server, NVD allows 5 requests per 30 seconds, and each package needs several requests; the progress line says "NVD rate limit without API key". If NVD is busy or slow, packages are marked Lookup failed with the reason; press Retry scan — packages already resolved are not sent again.

"This analysis has expired or was cleared" or "You already have scans running"

Scan jobs live only in server memory and expire 60 minutes after finishing, or when the server restarts; press Retry scan. At most two scans per client run at the same time, so wait or clear one.

Common mistakes

  • Reading "No known CVEs" as "secure". It means NVD lists none for that CPE and version; other databases may.
  • Ignoring "Unable to determine". Those components were not checked at all and are not part of the risk score.
  • Trusting possible matches blindly. They may belong to a different product with the same name.
  • Upgrading only the transitive package. Usually the direct dependency on the path has to be updated, or an override set in your package manager.
  • Treating the risk score as a standard. It is a NetTools heuristic for comparing SBOMs, not a CVSS score or compliance metric.
  • Analyzing a stale SBOM. The result describes the file, not what is running in production.

Limitations

  • One vulnerability source: only NVD is queried in this version; OSV, GitHub security advisories and distribution or vendor feeds are not.
  • CPE coverage: packages without an NVD CPE cannot be matched, and NVD's analysis of new CVEs can lag behind publication.
  • Speed: NVD rate limits mean large SBOMs take minutes; 5,000 unique packages per scan, 20,000 components and 25 MB per file.
  • Formats: CycloneDX 1.2–1.6 JSON/XML and SPDX 2.2/2.3 JSON only.
  • No reachability: the tool does not know whether vulnerable code is used, configured or exposed.
  • Fixed versions exist only where NVD states versionEndExcluding; the recommended version comes from version strings, not from compatibility testing.
  • Graph size: at most 500 nodes are drawn at once; reduce the depth or show only vulnerable paths for large trees.

Security & privacy

The SBOM never leaves your browser. Only per-package identifiers — key, name, version, PURL, CPE and ecosystem — go to the NetTools.tech API, which queries NVD from the server; your browser does not contact NVD. Scan jobs are held in memory only, not written to disk or logs, and deleted as described above. The "Detected in your SBOM" context on CVE pages stays in your browser tab. Internal package names in the SBOM (such as private npm scopes) are sent as identifiers, so remove them first if even their names are confidential. The tool needs no credentials. See the privacy policy.

Summary

The SBOM Security Analyzer parses CycloneDX and SPDX SBOMs in the browser, shows components, dependency paths and SBOM quality, and checks identifiable packages against NVD through CPE names, never by name alone. Every finding carries its match confidence and NVD's fixed version where one exists. Treat "Unable to determine" as unchecked, verify possible matches, and remember that NVD is the only source in this version.

Frequently asked questions

Which SBOM formats does the analyzer support?

CycloneDX 1.2 to 1.6 in JSON or XML, and SPDX 2.2 and 2.3 in JSON. SPDX tag-value, SPDX RDF/XML and SPDX 3.0 (JSON-LD) are rejected with a message asking for SPDX 2.x JSON, and CycloneDX XML with a DOCTYPE or entity declaration is refused.

Is my SBOM uploaded to the NetTools server?

No. The file is read and parsed in your browser. For vulnerability matching only package identifiers are sent: a de-duplication key, name, version, PURL, CPE and ecosystem. The server keeps the scan job in memory and deletes it when you press Clear analysis, load another SBOM or leave the page, and at the latest 60 minutes after the scan finished.

Where does the vulnerability data come from?

In this version only from NVD, the U.S. National Vulnerability Database, through the same data layer as the NetTools CVE Search. OSV, GitHub security advisories and vendor feeds are not queried yet, so vulnerabilities that exist only in those databases are not shown.

Why are many of my npm packages shown as Unable to determine?

NVD only knows products that have a CPE name, and many small npm, PyPI or Go packages have never been given one. When NVD's CPE dictionary has no entry for the package name, the analyzer reports Unable to determine instead of matching by name alone, which could attach CVEs of an unrelated product.

What is the difference between exact, strong and possible matches?

Exact means the SBOM itself contained a versioned CPE and NVD was asked about exactly that CPE. Strong means the PURL name and version were found in NVD's CPE dictionary with one consistent vendor; possible means the dictionary match was ambiguous (several vendors, ecosystem not confirmed, or the version not listed), so the CVE must be verified by hand.

Why does a scan take several minutes?

Every unique package needs at least a CPE dictionary lookup and a CVE query at NVD, and NVD allows only 5 requests per 30 seconds without an API key. The server paces requests within that limit, so it estimates about 13 seconds per package without a key and about 1.4 seconds with one; results are cached, so repeating a scan is faster.

How is the SBOM risk score calculated?

Each finding (CVE times component) earns points: Critical 10, High 5, Medium 2, Low 0.5, not scored 1. Direct dependencies count 1.5 times, CISA KEV listing adds 5 and possible matches count half; the score is 100 × (1 − e^(−points/50)), rounded. It is a NetTools assessment, not an industry standard, and components that could not be matched are not part of it.

Where does the recommended version come from?

From NVD's affected version ranges: for each CVE the lowest versionEndExcluding above your installed version for the matched product. The recommendation is the highest of these, so that one upgrade covers every CVE with a stated fix; CVEs without a fixed version in NVD are listed separately and nothing is guessed.

Does the analyzer tell me whether the vulnerable code is actually used?

No. It reports which components and versions in the SBOM have CVEs that NVD considers applicable, and how they enter the application. Whether a vulnerable function is reachable, configured or exposed in your deployment is outside what an SBOM can show.