CVE-2023-31044
Nokia Impact Mobile 19.11 – 23
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:NSummary
CVE-2023-31044 is a low-severity Code Injection (CWE-94) vulnerability in Nokia Impact Mobile. Its CVSS base score is 2.0 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-31044 is a code injection vulnerability (CWE-94) discovered in Nokia Impact versions before Mobile 23_FP1, specifically affecting Impact DM 19.11 and later. A remote authenticated user can exploit the Add Campaign functionality by injecting a malicious payload into the Campaign Name field. This payload persists in data exported to a CSV file, with a CVSS v3.1 base score of 2.0 (AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N), indicating low severity due to high attack complexity, required privileges, and user interaction.
Exploitation requires a remote authenticated user with high privileges (PR:H) to create a campaign with the injected payload. When an authorized user exports campaigns to CSV and opens the file in spreadsheet software, the payload in the populated data fields may trigger automatic execution, potentially leading to low-impact confidentiality breaches such as data exfiltration or other malicious activities.
Mitigation details are outlined in advisories available at https://nokia.com and https://www.gruppotim.it/it/footer/red-team/2023/Motive-Impact-CVE-2023-31044.html. Affected systems should be upgraded to Nokia Impact Mobile 23_FP1 or later to address the issue.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-35381
Vulnerability Data
An issue was discovered in Nokia Impact before Mobile 23_FP1. In Impact DM 19.11 onwards, a remote authenticated user, using the Add Campaign functionality, can inject a malicious payload within the Campaign Name. This data can be exported to a…
more
CSV file. Attackers can populate data fields that may attempt data exfiltration or other malicious activity when automatically executed by the spreadsheet software.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation finds code paths that accept and execute externally influenced strings.
Input validation directly stops untrusted data from being used to construct executable code without neutralization.
Least privilege limits the damage an injected code fragment can perform once executed.
Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.
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's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.
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.
Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.
Controls that restrict unauthorized or malicious code from being introduced via external networks or removable media limit opportunities for an attacker to inject and execute arbitrary code.