Skip to content
Fencer Intel
medium 5.9

CVE-2021-43767 json

Odyssey passes to client unencrypted bytes from man-in-the-middle When Odyssey storage is configured to use the PostgreSQL server using 'tr…

published 4y ago modified 2mo ago also BIT-postgresql-2021-43767 , EUVD-2021-30674 , JLSEC-2026-36

cvss
5.9
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

Odyssey passes to client unencrypted bytes from man-in-the-middle When Odyssey storage is configured to use the PostgreSQL server using 'trust' authentication with a 'clientcert' requirement or to use 'cert' authentication, a man-in-the-middle attacker can inject false responses to the client's first few queries. Despite the use of SSL certificate verification and encryption, Odyssey will pass these results to client as if they originated from valid server. This is similar to CVE-2021-23222 for PostgreSQL.

Patch / fix

  • bitnami postgresql 9.6.24, 10.19.0, 11.14.0, 12.9.0, 13.5.0, 14.0.1
  • julia LibPQ_jll 14.1.0+0
  • postgresql postgresql 9.6.24, 10.19, 11.14, 12.9, 13.5

Is CVE-2021-43767 in your dependencies? 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

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
bitnami postgresql
>=9.6.0, <9.6.24
>=10.0.0, <10.19.0
>=11.0.0, <11.14.0
>=12.0.0, <12.9.0
>=13.0.0, <13.5.0
>=14.0.0, <14.0.1
9.6.24
10.19.0
11.14.0
12.9.0
13.5.0
14.0.1
julia LibPQ_jll
<14.1.0+0
14.1.0+0

Affected products

  • n/a Odyssey

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
  • CWE-295 Improper Certificate Validation
Technology feeds

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.