Skip to content
Fencer Intel
high 8.8

CVE-2016-3072 json

Katello SQL Injection vulnerabilities

published 2016-06-07 10 y ago modified 2026-06-17 4 mo ago also GHSA-527r-mfmj-prqf , EUVD-2022-2474

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

Summary

Multiple SQL injection vulnerabilities in the scoped_search function in app/controllers/katello/api/v2/api_controller.rb in Katello allow remote authenticated users to execute arbitrary SQL commands via the (1) sort_by or (2) sort_order parameter.

Patch / fix

  • rubygems katello 2.4.3
  • ruby193-rubygem-katello satellite 6.1 2.2.0.86-1.el6_6sat
  • ruby193-rubygem-katello satellite 6.1 2.2.0.86-1.el7sat

red hat advisories RHSA-2016:1083

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-2016-3072 updated cvss 6.5

Katello: Authenticated sql injection via sort_by and sort_order request parameter

  • Red Hat Satellite 6.1 ruby193-rubygem-katello 2.2.0.86-1.el7sat, ruby193-rubygem-katello 2.2.0.86-1.el6_6sat
    fixed: vendor fix RHSA-2016:1083
  • Red Hat Subscription Asset Manager katello
    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.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
rubygems katello
<2.4.3
2.4.3

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

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.