dbcve.org
OtrsApplication

CVE-2020-1773

HIGH · 8.1 CVSS v3.1 Published 2020-03-27
Fix available
A fix is available. Upgrade to after 7.0.15 or later.
See remediation →
87/100
Remediation priority · High
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
An attacker with the ability to generate session IDs or password reset tokens, either by being able to authenticate or by exploiting OSA-2020-09, may be able to predict other users session IDs, password reset tokens and automatically generated passwords. This issue affects ((OTRS)) Community Edition: 5.0.41 and prior versions, 6.0.26 and prior versions. OTRS; 7.0.15 and prior versions.

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

Insufficient randomness in the session ID, password reset token, and automatically generated password generation algorithm in OTRS allows an attacker who can generate tokens (through authentication or OSA-2020-09) to predict and hijack other users' sessions and reset tokens.

MitigationUpgrade OTRS to version 5.0.42, 6.0.27, or 7.0.16 or later which implement proper cryptographic randomness in token generation.

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
OtrsApplication
Affected:>= 5.0.0, <= 5.0.41>= 6.0.0, <= 6.0.26>= 7.0.0, <= 7.0.15

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 OTRS installation and version
    Locate the Kernel/VERSION.pm file in your OTRS installation directory and read the version number from it, or run 'perl -MOTRS -e 'print $OTRS::Version::String' from the OTRS home directory.
    Affected if The installed version falls within 5.0.0-5.0.41, 6.0.0-6.0.26, or 7.0.0-7.0.15.
  2. Confirm OTRS web interface is accessible
    Verify that the OTRS web interface is reachable and operational.
    Affected if OTRS is exposed and accessible to generate tokens through authentication.
  3. Check for recent authentication or password reset activity
    Review OTRS system logs for authentication events and password reset token generation.
    Affected if The system has processed authentication requests or password resets, enabling token generation that could be exploited.

You are affected if your OTRS version is between 5.0.0 and 5.0.41, between 6.0.0 and 6.0.26, or between 7.0.0 and 7.0.15, and the application is accessible for token generation.

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 7.0.15
Interim mitigation

Upgrade OTRS to version 5.0.42, 6.0.27, or 7.0.16 or later which implement proper cryptographic randomness in token generation.

Fix this in Otrs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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