dbcve.org
Debian LinuxOperating system · Debian

CVE-2019-18890

MEDIUM · 6.5 CVSS v3.1 Published 2019-11-21
Fix available
A fix is available. Upgrade to 3.3.10 or later.
See remediation →
71/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
A SQL injection vulnerability in Redmine through 3.2.9 and 3.3.x before 3.3.10 allows Redmine users to access protected information via a crafted object query.

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

SQL injection in Redmine's object query mechanism allows authenticated users to inject malicious SQL statements, bypassing intended access controls and exposing protected data from the database.

MitigationUpgrade Redmine to version 3.3.10 or later (or latest stable release) to patch the SQL injection vulnerability. Review access logs for indicators of exploitation targeting the object query functionality.

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
Debian LinuxOperating system
Affected:= 9.0
RedmineApplication
Affected:< 3.3.10

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    Run `ruby -e "require 'redmine'; puts Redmine::VERSION.to_s"` or check the VERSION file in the Redmine root directory
    Affected if The installed version is lower than 3.3.10 (e.g., 3.3.9, 3.3.0, 2.x series)
  2. Confirm Debian version
    Run `cat /etc/debian_version` to check the installed Debian version
    Affected if The system runs Debian 9.0 (used in conjunction with vulnerable Redmine versions)
  3. Verify object query feature access
    Check if the REST API or object query endpoints are accessible to authenticated users by reviewing Redmine's routes configuration and user role permissions
    Affected if Authenticated users have access to the object query API functionality
  4. Review access logs for SQL injection indicators
    Inspect Redmine logs (log/production.log or log/development.log) and web server access logs for unusual SQL syntax in request parameters, particularly on API/query endpoints
    Affected if Log entries contain SQL fragments or unexpected characters in query parameters that suggest exploitation attempts

A user is affected if running Redmine versions prior to 3.3.10 with authenticated access to the object query mechanism, particularly on Debian 9.0 systems.

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 3.3.10 or later
Fixed in 3.3.10
Interim mitigation

Upgrade Redmine to version 3.3.10 or later (or latest stable release) to patch the SQL injection vulnerability. Review access logs for indicators of exploitation targeting the object query functionality.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18890 — 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-2019-18890 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