Skip to content
Fencer Intel
medium 6.5

CVE-2019-6460 json

An issue was discovered in GNU Recutils 1.8.

published 7y ago modified 4mo ago also EUVD-2019-16020

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

An issue was discovered in GNU Recutils 1.8. There is a NULL pointer dereference in the function rec_field_set_name() in the file rec-field.c in librec.a.

Patch / fix

  • recutils Ubuntu Pro 16.04 LTS 1.7-1ubuntu0.1~esm1
  • recutils Ubuntu Pro 18.04 LTS 1.7-2ubuntu0.1~esm1
  • recutils Ubuntu Pro 20.04 LTS 1.8-1ubuntu0.20.04.1~esm1
  • recutils Ubuntu Pro 22.04 LTS 1.8-1ubuntu0.22.04.1~esm1

ubuntu advisories UBUNTU-CVE-2019-6460

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-6460 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-2019-6460 updated cvss 4.3

recutils: Multiple security issues

  • 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.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/TeamSeri0us/pocs/tree/master/recutils referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

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.