CVE-2022-27648 [High] | Security Vulnerability in Screen Creator Advance 2

This vulnerability allows remote attackers to execute arbitrary code on affected installations of KOYO Screen Creator 0.1.1.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of SCA2 files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14868.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-17	2.01%	0.40%	-1.62%
2	2026-03-31	2.10%	2.01%	-0.09%
3	2026-03-30	—	2.10%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-17

2.01%

0.40%

-1.62%

2026-03-31

2.10%

2.01%

-0.09%

2026-03-30

—

2.10%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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: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: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.	1.8	5.9	[email protected]
7.8	3.0	HIGH	`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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: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: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.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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: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: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.

1.8

5.9

[email protected]

7.8

3.0

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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: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: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.

1.8

5.9

[email protected]

Affected software / configurations for CVE-2022-27648

Vendor	Product	Version	Raw CPE
jtekt	screen_creator_advance_2	< 0.1.1.4	cpe:2.3:a:jtekt:screen_creator_advance_2::::::::
jtekt	screen_creator_advance_2	0.1.1.4	cpe:2.3:a:jtekt:screen_creator_advance_2:0.1.1.4:-::::::
jtekt	screen_creator_advance_2	0.1.1.4	cpe:2.3:a:jtekt:screen_creator_advance_2:0.1.1.4:build01::::::
jtekt	screen_creator_advance_2	0.1.1.4	cpe:2.3:a:jtekt:screen_creator_advance_2:0.1.1.4:build01b::::::
jtekt	screen_creator_advance_2	0.1.1.4	cpe:2.3:a:jtekt:screen_creator_advance_2:0.1.1.4:build02::::::

References for CVE-2022-27648

URL	Tags
https://www.koyoele.co.jp/en/topics/202203154994/	Vendor Advisory
https://www.zerodayinitiative.com/advisories/ZDI-22-543/	Third Party Advisory VDB Entry

URL

CVE-2022-27648

Exploit prediction scoring system (EPSS) score for CVE-2022-27648

Common vulnerability scoring system (CVSS) metrics for CVE-2022-27648

Weakness enumeration for CVE-2022-27648

Affected software / configurations for CVE-2022-27648

References for CVE-2022-27648