dbcve.org
RedmineApplication

CVE-2012-2054

MEDIUM · 5.0 CVSS v2.0 Published 2012-04-05
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Redmine before 1.3.2 does not properly restrict the use of a hash to provide values for a model's attributes, which allows remote attackers to set attributes in the (1) Comment, (2) Document, (3) IssueCategory, (4) MembersController, (5) Message, (6) News, (7) TimeEntry, (8) Version, (9) Wiki, (10) UserPreference, or (11) Board model via a modified URL, related to a "mass assignment" vulnerability, a different vulnerability than CVE-2012-0327.

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

Redmine before 1.3.2 contains a mass assignment vulnerability where the application improperly uses a hash to assign model attributes from HTTP request parameters. Attackers can craft modified URLs to set arbitrary attributes on 11 different models (Comment, Document, IssueCategory, MembersController, Message, News, TimeEntry, Version, Wiki, UserPreference, Board), bypassing intended access controls.

MitigationUpgrade to Redmine 1.3.2 or later, which implements proper attribute protection. Alternatively, implement strong parameter filtering in the affected controllers to whitelist allowed attributes.

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
RedmineApplication
Affected:<= 1.3.1= 0.1.0= 0.2.1= 0.2.2= 0.3.0= 0.4.0= 0.4.1= 0.4.2= 0.5.0= 0.5.1= 0.6.0= 0.6.1

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
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/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. Identify Redmine version
    Check the version.rb file in the Redmine installation (app/models/issue.rb or VERSION file in the root) or run: cat /path/to/redmine/VERSION
    Affected if The version is 1.3.1 or lower, or matches one of these: 0.1.0, 0.2.1, 0.2.2, 0.3.0, 0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.5.1, 0.6.0, 0.6.1
  2. Locate affected controllers
    Identify controllers handling these models: Comment, Document, IssueCategory, MembersController, Message, News, TimeEntry, Version, Wiki, UserPreference, Board. Search in app/controllers/ directory for files like comments_controller.rb, documents_controller.rb, issue_categories_controller.rb, members_controller.rb, messages_controller.rb, news_controller.rb, time_entries_controller.rb, versions_controller.rb, wiki_controller.rb, user_preferences_controller.rb, boards_controller.rb
    Affected if Any of these controllers exist and use model attribute assignment from request parameters without explicit attribute whitelisting
  3. Inspect model attribute protection
    Check each affected model file in app/models/ for use of attr_accessible or attr_protected. Look for patterns like 'attr_accessible :attr_name' which indicates protection, or absence of such declarations which indicates vulnerability. Example: cat app/models/issue_category.rb
    Affected if The models lack attr_accessible declarations or have overly permissive mass assignment allowing arbitrary attributes from user input
  4. Test parameter-based attribute assignment
    Identify controller actions that accept parameters and pass them directly to model creation or update methods like Model.new(params[:model]) or model.update_attributes(params[:model]). Attempt a test request with an unexpected attribute parameter to see if it is accepted.
    Affected if Controllers accept and process arbitrary attributes from HTTP parameters without filtering which attributes can be assigned

If the installed Redmine version is 1.3.1 or earlier, or is one of the listed 0.x versions, AND the application uses direct parameter-to-model assignment without attribute whitelisting on the 11 affected controllers, the environment is vulnerable to CVE-2012-2054.

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.3.1
Interim mitigation

Upgrade to Redmine 1.3.2 or later, which implements proper attribute protection. Alternatively, implement strong parameter filtering in the affected controllers to whitelist allowed attributes.

Fix this in Redmine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2054 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