CVE-2020-1772 [Medium] | Information Disclosure in Otrs

It's possible to craft Lost Password requests with wildcards in the Token value, which allows attacker to retrieve valid Token(s), generated by users which already requested new 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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.45%	1.62%	+1.17%
2	2026-03-04	0.59%	0.45%	-0.14%
3	2025-12-28	—	0.59%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.45%

1.62%

+1.17%

2026-03-04

0.59%

0.45%

-0.14%

2025-12-28

—

0.59%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.2	4.2	[email protected]
7.5	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.9	3.6	[email protected]
5.0	2.0	MEDIUM	`AV:N/AC:L/Au:N/C:P/I:N/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:N) No availability impact.	10.0	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.2

4.2

[email protected]

7.5

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.9

3.6

[email protected]

5.0

2.0

MEDIUM

AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:N): No availability impact.

10.0

2.9

[email protected]

OS Trackers for CVE-2020-1772

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2020-1772 not yet assigned priority: Debian including 1 source packages (otrs2), 1 status rows across 1 suites (bullseye): resolved 1.	https://security-tracker.debian.org/tracker/CVE-2020-1772
`ubuntu`	medium	CVE-2020-1772 medium priority: Ubuntu including 1 source packages (otrs2), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 8, needs-triage 4, not-affected 4, ignored 1.	https://ubuntu.com/security/CVE-2020-1772

Affected software / configurations for CVE-2020-1772

Vendor	Product	Version	Raw CPE
otrs	otrs	>= 5.0.0, <= 5.0.41	cpe:2.3:a:otrs:otrs:::::community:::*
otrs	otrs	>= 6.0.0, <= 6.0.26	cpe:2.3:a:otrs:otrs:::::community:::*
otrs	otrs	>= 7.0.0, <= 7.0.15	cpe:2.3:a:otrs:otrs::::::::
opensuse	backports_sle	15.0	cpe:2.3:a:opensuse:backports_sle:15.0:-::::::
opensuse	backports_sle	15.0	cpe:2.3:a:opensuse:backports_sle:15.0:sp1::::::
opensuse	backports_sle	15.0	cpe:2.3:a:opensuse:backports_sle:15.0:sp2::::::
opensuse	leap	15.1	cpe:2.3:o:opensuse:leap:15.1:::::::*
opensuse	leap	15.2	cpe:2.3:o:opensuse:leap:15.2:::::::*
debian	debian_linux	8.0	cpe:2.3:o:debian:debian_linux:8.0:::::::*

References for CVE-2020-1772

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00038.html	Mailing List Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00066.html	Mailing List Third Party Advisory
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00077.html	Mailing List Third Party Advisory
https://lists.debian.org/debian-lts-announce/2020/05/msg00000.html	Mailing List Third Party Advisory
https://lists.debian.org/debian-lts-announce/2023/08/msg00040.html
https://otrs.com/release-notes/otrs-security-advisory-2020-09/	Patch Vendor Advisory

URL

CVE-2020-1772 | Information Disclosure

Exploit prediction scoring system (EPSS) score for CVE-2020-1772

Common vulnerability scoring system (CVSS) metrics for CVE-2020-1772

Weakness enumeration for CVE-2020-1772

OS Trackers for CVE-2020-1772

Affected software / configurations for CVE-2020-1772

References for CVE-2020-1772