Skip to content
Fencer Intel
medium 5.3

CVE-2018-16737 json

tinc before 1.0.30 has a broken authentication protocol, without even a partial mitigation.

published 8y ago modified 4mo ago also EUVD-2018-8537

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

Summary

tinc before 1.0.30 has a broken authentication protocol, without even a partial mitigation.

Patch / fix

  • tinc-vpn tinc 1.0.30
  • tinc Debian 14, Debian 13, Debian 12 1.0.31-1

debian advisories DEBIAN-CVE-2018-16737

  • tinc openSUSE Tumbleweed 1.0.36-1.9

opensuse advisories openSUSE-SU-2024:11463-1

  • tinc Alpine 3.24, Alpine 3.23, Alpine 3.22 +13 more 1.0.35-r0

alpine advisories ALPINE-CVE-2018-16737

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-16737 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-16737 updated cvss 7.3

tinc: Multiple issues fixed in the 1.0.35 release

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness

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.