katello

CVE-2016-3072

CVE-2016-3072 is a high-severity SQL injection vulnerability in katello (rubygems), affecting versions < 2.4.3. It is fixed in 2.4.3.

Key facts
CVSS score
8.8
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
katello
Fixed in
2.4.3
Disclosed
2016

Summary

Multiple SQL injection vulnerabilities in the scopedsearch function in app/controllers/katello/api/v2/apicontroller.rb in Katello allow remote authenticated users to execute arbitrary SQL commands via the (1) sortby or (2) sortorder parameter.

Impact

What is SQL injection?

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Severity and exposure

CVE-2016-3072 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.4.3). Upgrading removes the vulnerable code path.

Affected versions

rubygems

  • katello (< 2.4.3)

Security releases

  • katello → 2.4.3 (rubygems)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2016-3072 is reachable in your applications. Explore open-source security for your team.

See if CVE-2016-3072 is reachable in your applications. Get a demo

Remediation advice

Upgrade katello to 2.4.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2016-3072

What is CVE-2016-3072?

CVE-2016-3072 is a high-severity SQL injection vulnerability in katello (rubygems), affecting versions < 2.4.3. It is fixed in 2.4.3. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2016-3072?

CVE-2016-3072 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of katello are affected by CVE-2016-3072?

katello (rubygems) versions < 2.4.3 is affected.

Is there a fix for CVE-2016-3072?

Yes. CVE-2016-3072 is fixed in 2.4.3. Upgrade to this version or later.

Is CVE-2016-3072 exploitable, and should I be worried?

Whether CVE-2016-3072 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2016-3072 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2016-3072?

Upgrade katello to 2.4.3 or later.

Stop the waste.
Protect your environment with Kodem.