Cyber Resilience

CVE-2024-34698

Freescout ≤ 1.8.139

Public PoC
Published
14 May 2024
Modified
10 January 2025
Patch / advisory
CVSS Score v3.1 4.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
EPSS Score 0.0046 38th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2024-34698 is a medium-severity Prototype Pollution (CWE-1321) vulnerability in Freescout Freescout. Its CVSS base score is 4.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

FreeScout is a free, self-hosted help desk and shared mailbox. Versions of FreeScout prior to 1.8.139 contain a Prototype Pollution vulnerability in the `/public/js/main.js` source file. The Prototype Pollution arises because the `getQueryParam` Function recursively merges an object containing user-controllable…

more

properties into an existing object (For URL Query Parameters Parsing), without first sanitizing the keys. This can allow an attacker to inject a property with a key `__proto__`, along with arbitrarily nested properties. The merge operation assigns the nested properties to the `params` object's prototype instead of the target object itself. As a result, the attacker can pollute the prototype with properties containing harmful values, which are then inherited by user-defined objects and subsequently used by the application dangerously. The vulnerability lets an attacker control properties of objects that would otherwise be inaccessible. If the application subsequently handles an attacker-controlled property in an unsafe way, this can potentially be chained with other vulnerabilities like DOM-based XSS, Open Redirection, Cookie Manipulation, Link Manipulation, HTML Injection, etc. Version 1.8.139 contains a patch for the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-58163Same product: Freescout Freescout
CVE-2025-54366Same product: Freescout Freescout
CVE-2025-48389Same product: Freescout Freescout
CVE-2026-32754Same product: Freescout Freescout
CVE-2026-28289Same product: Freescout Freescout
CVE-2024-1932Same product: Freescout Freescout
CVE-2024-29185Same product: Freescout Freescout
CVE-2026-27636Same product: Freescout Freescout
CVE-2025-48471Same product: Freescout Freescout
CVE-2025-48388Same product: Freescout Freescout

Affected Assets

freescout
freescout
≤ 1.8.139

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches prototype-pollution flaws before release.

prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References