Skip to content

fix: remediate Example TA dependency vulnerabilities - #48

Merged
Sukupate merged 1 commit into
mainfrom
fix/vulns-splunk-example-ta-batch-20260909T000000Z
Sep 23, 2026
Merged

Sukupate merged 1 commit into
mainfrom
fix/vulns-splunk-example-ta-batch-20260909T000000Z

Conversation

@Sukupate

@Sukupate Sukupate commented Sep 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Remediates five dependency vulnerability tickets in the Example TA UI dependency graph.

Remediated tickets

  • VULN-108207: jsonata 2.0.6 → 2.2.0
  • VULN-108190: js-yaml 4.1.0 → 4.3.0
  • VULN-108187: js-yaml 3.14.1 → 3.15.0
  • VULN-108052: protocol-buffers-schema 3.6.0 → 3.6.1
  • VULN-108008: fast-uri 3.0.6 → 3.1.5

Validation

  • Clean npm install from ui/package-lock.json
  • Jest: 4 tests passed
  • ESLint and Prettier passed
  • Production webpack build passed

Jira closure

After merge and fresh FOSSA verification, close each ticket with VEX status resolved and justification upgraded_to_safe_version.

Upgrade jsonata to 2.2.0, js-yaml to 4.3.0 and 3.15.0, protocol-buffers-schema to 3.6.1, and fast-uri to 3.1.5.\n\nTickets: VULN-108207, VULN-108190, VULN-108187, VULN-108052, VULN-108008
@Sukupate
Sukupate merged commit 8ad417d into main Sep 23, 2026
12 checks passed
@Sukupate
Sukupate deleted the fix/vulns-splunk-example-ta-batch-20260909T000000Z branch September 23, 2026 11:15
Sukupate added a commit that referenced this pull request Oct 23, 2026
## Summary

Fixes the remaining vulnerable UUID copy found while reassessing
[VULN-109578](https://splunk.atlassian.net/browse/VULN-109578),
CVE-2026-41907.

The existing remediation upgraded the top-level UUID dependency to
11.1.1. The development dependency chain `webpack-dev-server ->
sockjs@0.3.24 -> uuid@8.3.2` still introduced an affected copy.

- Add a scoped npm override for `sockjs@0.3.24` to use UUID 11.1.1.
- Regenerate `ui/package-lock.json`; the nested UUID 8.3.2 entry is
removed and SockJS resolves the existing UUID 11.1.1 copy.
- Use `chore:` because the changed dependency belongs to development
server tooling.

## Why a scoped override

SockJS 0.3.24 is the current upstream version and still declares UUID
`^8.3.2`. Every available webpack-dev-server 5.x version, including
5.2.7, retains SockJS `^0.3.24`. A lockfile refresh or parent update
within that major cannot select the patched UUID version.

SockJS calls `require('uuid').v4()` without arguments. UUID 11.1.1
retains the CommonJS export and this API. The override is limited to
this exact SockJS version.

Upstream advisory: GHSA-w5hq-g745-h8pq

## Validation

- `npm install --package-lock-only --ignore-scripts --no-audit --no-fund
--registry=https://registry.npmjs.org` completed successfully.
- Inspected every UUID lockfile entry: only 11.1.1 remains.
- Compared every installed dependency copy relevant to all 27 Example TA
findings against the affected ranges in their 21 current upstream
advisories; no matching affected version remains in this branch.
- Inspected the published SockJS 0.3.24 source and UUID 11.1.1 export
metadata for the API compatibility described above.
- `git diff --check` passed.

No unit tests, lint, production build, or runtime compatibility tests
were run for this patch. CI results remain to be reviewed; pipeline
completion was not awaited.

## Jira

Keep VULN-109578 open until this follow-up fix is merged and the target
branch is rechecked. The other 26 queue findings were already fixed by
merged PRs #45–#48 and have been reclosed separately with `Resolved /
upgraded_to_safe_version` after current-branch and advisory
verification.

Prepared with AI assistance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant