Home
» Security vulnerabilities
» CVE-2022-3798
A vulnerability classified as critical has been found in IBAX go-ibax. Affected is an unknown function of the file /api/v2/open/tablesInfo. The manipulation leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-212634 is the identifier assigned to this vulnerability.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-3798
Conclusion & alert: CVE-2022-3798 is rated Moderate Risk (43.2/100) : CVSS Medium severity, with medium exploitation likelihood (EPSS 0.28%).Mandatory action: Review affected assets and schedule remediation.
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-3798
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-11-21
0.22%
0.28%
+0.07%
2
2025-11-18
0.28%
0.22%
-0.07%
3
2025-11-10
—
0.28%
—
Full EPSS history
(12 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-3798
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
6.3
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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: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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.8
3.4
[email protected]
8.8
3.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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: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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8
5.9
[email protected]
Weakness enumeration for CVE-2022-3798
GitHub Security Advisory for CVE-2022-3798
GHSA-mgqh-3qm7-gx82 · Severity: high · Ecosystem: go
— IBAX go-ibax vulnerable to SQL injection
Affected software / configurations for CVE-2022-3798
Vendor
Product
Version
Raw CPE
ibax
go-ibax
—
cpe:2.3:a:ibax:go-ibax:-:*:*:*:*:*:*:*
References for CVE-2022-3798
cvelogic
Threat Intelligence