Application crash via oversized tab name
Published Jan 16, 2026 · Updated Jan 16, 2026
Improper input validation in Splinterware iDailyDiary 4.30 allows local users to crash the application via an oversized tab name. The Preferences Tabs field accepts a pasted 2,000,000-character default diary tab name and processes it when Apply is selected without enforcing a safe length limit. Exploitation requires access to the Windows desktop interface and interrupts only the running diary application; no confidentiality or integrity impact is reported.
Summary
What happened
Improper input validation in Splinterware iDailyDiary 4.30 allows local users to crash the application via an oversized tab name. The Preferences Tabs field accepts a pasted 2,000,000-character default diary tab name and processes it when Apply is selected without enforcing a safe length limit. Exploitation requires access to the Windows desktop interface and interrupts only the running diary application; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2021-47824
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- Splinterware
- Product
- iDailyDiary
- Classifications
- CWE-1284, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.30
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- iDailyDiary 4.30 denial-of-service PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo