CloudformsApplication · Redhat

CVE-2012-5603

MEDIUM · 5.5 CVSS v2.0 Published 2013-01-04
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
proxies_controller.rb in Katello in Red Hat CloudForms before 1.1 does not properly check permissions, which allows remote authenticated users to read consumer certificates or change arbitrary users' settings via unspecified vectors related to the "consumer UUID" of a system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The proxies_controller.rb in Katello (Red Hat CloudForms before 1.1) lacks proper permission validation when handling requests containing a 'consumer UUID'. Authenticated users can exploit this by manipulating the consumer UUID parameter to read consumer certificates or modify arbitrary user settings, effectively bypassing authorization controls.

MitigationUpgrade to Red Hat CloudForms 1.1 or later which includes the patched Katello version with proper permission checks in proxies_controller.rb.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CloudformsApplication
Affected:<= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:S/C:P/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Red Hat CloudForms is installed
    Locate CloudForms installation directories or check system services for 'cloudforms' or 'katello' components. Common paths include /opt/cloudforms, /usr/share/katello, or check via system package manager.
    Affected if CloudForms or Katello components are found on the system
  2. Determine the installed CloudForms version
    Run command to retrieve CloudForms version, such as: rpm -q cloudforms-management-engine or check katello package version via rpm -qa | grep katello. Also check /opt/cloudforms/version or similar version file if it exists.
    Affected if Version returned is 1.0 or lower (1.0.x, 0.x, or unpatched versions)
  3. Verify Katello proxies_controller.rb is present
    Locate the Katello proxies_controller.rb file in the Rails application directory, typically under /usr/share/katello/app/controllers/proxies_controller.rb or within the CloudForms engine directory.
    Affected if The file exists and originates from a Katello version bundled with CloudForms <= 1.0
  4. Check for missing authorization logic in proxies_controller.rb
    Inspect the proxies_controller.rb file for the consumer UUID parameter handling. Look for authorization checks around lines handling the 'consumer_uuid' or 'consumer' parameters. Search for patterns like 'authorize' or 'allowed?' or 'permission' near consumer UUID processing.
    Affected if No authorization checks are found before consumer UUID operations, allowing parameter manipulation

User is affected if Red Hat CloudForms version is 1.0 or lower AND the Katello proxies_controller.rb lacks proper permission validation for consumer UUID parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Upgrade to Red Hat CloudForms 1.1 or later which includes the patched Katello version with proper permission checks in proxies_controller.rb.

Fix this in Cloudforms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5603 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5603 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data