VulnerabilityPublished 7 Dec 2023Updated 28 May 2025

CVE-2023-43304: PARK DANDAN mini-app · Authentication Bypass by Spoofing

Source CVE Database V5

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =13.6.1	Fixed in–

AI-suggested

Given the absence of official patches, European organizations should take immediate steps to mitigate the risk: 1) Restrict and monitor access to channel access tokens rigorously, ensuring they are stored securely and rotated frequently to limit exposure. 2) Implement anomaly detection on messaging patterns to identify and block suspicious notifications that do not conform to expected behavior. 3) Educate users about the risk of phishing and malicious notifications, emphasizing verification of message authenticity before taking action. 4) Collaborate with Line platform administrators to report the vulnerability and seek guidance or temporary protective measures. 5) Consider limiting the use of the PARK DANDAN mini-app or Line messaging channels for sensitive communications until the vulnerability is resolved. 6) Employ endpoint security solutions capable of detecting and blocking malicious payloads delivered via messaging platforms. 7) Conduct regular security audits of third-party mini-apps integrated into organizational communication channels to identify potential token leakage or authentication weaknesses.

Description

An issue in PARK DANDAN mini-app on Line v13.6.1 allows attackers to send crafted malicious notifications via leakage of the channel access token.

Impact

For European organizations, the primary risk lies in the potential for attackers to send malicious notifications that could lead to phishing attacks, credential theft, or distribution of malware through social engineering. Organizations using Line and its mini-app ecosystem for customer engagement, internal communications, or marketing could see compromised trust and reputational damage if their users receive fraudulent messages. The confidentiality breach of the channel access token could also allow attackers to impersonate legitimate communications, increasing the risk of targeted attacks. While the vulnerability does not directly impact system availability or data integrity, the indirect effects on user security and organizational reputation could be significant. Sectors with high reliance on Line for communication, such as retail, finance, or customer service, are particularly vulnerable. Additionally, the lack of patches or mitigations at the time of disclosure increases the urgency for organizations to implement compensating controls.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/syz913/CVE-reports/blob/main/CVE-2023-43304.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 08:25 UTC

WeaknessesCWE-290

Technical details

References

Community reviews

Related threats