limbo.watch

In limbo for 1,292 days

GHSA-356r-rwp8-h6m6

github.com/effectindex/tripreporter on Go · published in effectindex/tripreporter

Read the advisory on GitHub ↗

Facts

Severity
Critical · CVSS score 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected versions
< bd80ba833b9023d39ca22e29874296c8729dd53bAs entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in
bd80ba833b9023d39ca22e29874296c8729dd53b
CVE
CVE-2023-31123 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use github.com/effectindex/tripreporter < bd80ba833b9023d39ca22e29874296c8729dd53b

The fixed-version field says “bd80ba833b9023d39ca22e29874296c8729dd53b”. Check the advisory for which version fixes it. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2023-04-30 12:18 UTC

    Published by the maintainers

    Cites CVE-2023-31123

  2. 2026-10-31 12:45 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-356r-rwp8-h6m6.json