Home
» Security vulnerabilities
» CVE-2022-3501
Article template contents with sensitive data could be accessed from agents without permissions.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-3501
Conclusion & alert: CVE-2022-3501 is rated Low Risk (27.5/100) : CVSS Low severity, with low exploitation likelihood (EPSS 0.17%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2022-3501
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2025-07-12
0.13%
0.17%
+0.03%
2
2025-03-30
0.23%
0.13%
-0.10%
3
2025-03-29
—
0.23%
—
Full EPSS history
(7 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-3501
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
3.5
3.1
LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.1
1.4
[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]
Weakness enumeration for CVE-2022-3501
OS Trackers for CVE-2022-3501
vendor
priority
summary
link
ubuntu
medium
CVE-2022-3501 medium priority: Ubuntu including 1 source packages (znuny), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, DNE 3, needs-triage 3.
https://ubuntu.com/security/CVE-2022-3501
Affected software / configurations for CVE-2022-3501
Vendor
Product
Version
Raw CPE
otrs
otrs
>= 8.0.0, < 8.0.26
cpe:2.3:a:otrs:otrs:*:*:*:*:*:*:*:*
References for CVE-2022-3501
cvelogic
Threat Intelligence