Cyber Resilience

CVE-2025-44017

Info Disclosure

Info Disclosure
Published
02 September 2025
Modified
17 June 2026
CVSS Score v4 5.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-44017 is a medium-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Jvn (inferred from references). Its CVSS base score is 5.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 14th 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

"Gunosy" App contains a vulnerability where sensitive information may be included in the application's outbound communication. If a user accesses a crafted URL, an attacker may obtain the JWT (JSON Web Token).

CWE(s)
CWE-201

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-13254Shared CWE-201
CVE-2025-32635Shared CWE-201
CVE-2025-49584Shared CWE-201
CVE-2025-69132Shared CWE-201
CVE-2025-7708Shared CWE-201
CVE-2026-32354Shared CWE-201
CVE-2025-59579Shared CWE-201
CVE-2025-53992Shared CWE-201
CVE-2025-64299Shared CWE-201
CVE-2025-13295Shared CWE-201

Affected Assets

Jvn
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

AC-3 Access Enforcement good match

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

SI-15 Information Output Filtering good match

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

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 prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
prevents

Protecting data-in-use includes removing confidential values before they are processed or sent.

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.

A.8.11 Data masking mostly match
prevents

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

A.5.12 Classification of information partial match
mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

A.5.13 Labelling of information partial match
mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

A.5.14 Information transfer partial match
mitigates

Information-transfer rules directly govern what data may be sent to external parties.

A.5.34 Privacy and protection of PII partial match
mitigates

PII-protection requirements reduce the chance of sending personal data to unauthorized recipients.

A.8.12 Data leakage prevention partial match
mitigates

DLP controls inspect and block outbound flows that contain sensitive information.

References