CVE-2021-44988

What it actually does

Stack overflow in ecma_find_named_property allows memory corruption on the call stack, enabling control-flow hijacking or process crash.

Why it matters to the business

Compromised JavaScript execution environments may expose sensitive data or allow remote code execution; moderate urgency due to low EPSS, stable trend, and no KEV listing despite exploit code being public.

How an attack unfolds

An attacker supplies crafted JavaScript that reaches ecma_find_named_property, overflows the stack frame, and overwrites return addresses or saved registers to gain arbitrary execution.

How to fix it

Upgrade neorazorx/facturascripts to commit 73a6595ca85984d65f656c6356fabb23d1936c54 or later; rebuild and redeploy any embedded JerryScript components.

How to confirm the fix worked

Confirm the ecma-helpers.c source contains the patched ecma_find_named_property implementation and that runtime tests exercising named-property lookups no longer trigger overflows.

Typical attack path

1. Deliver malicious JavaScript to the target application
2. Trigger property lookup that calls the vulnerable helper
3. Overflow the stack to corrupt control data
4. Execute attacker-supplied code or cause denial of service

How to detect it

Review application and system logs for unexpected crashes or stack-smashing signals during JavaScript execution; correlate with file or network sources that deliver untrusted scripts.

What your security team should do

• Apply the referenced commit immediately in all builds
• Scan source repositories for older JerryScript copies
• Add memory-safety tooling (ASAN, fuzzing) to the build pipeline
• Monitor upstream JerryScript releases for related fixes