Skip to content
Fencer Intel
high 7.5

GHSA-j2m3-f88h-2h46 json

pgEdge Spock apply worker allows remote code execution through an unchecked replicated tuple length header

published 20d ago modified 7d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository pgEdge/spock. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
7.5
version 3.1, the maintainers
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of pgEdge/spock: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Is GHSA-j2m3-f88h-2h46 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
the maintainers 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-125 Out-of-bounds Read
  • CWE-822 Untrusted Pointer Dereference
  • CWE-1284 Improper Validation of Specified Quantity in Input

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of pgEdge/spock published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.