dbcve.org
ValeappApplication · Oceanicsoft

CVE-2024-8644

HIGH · 7.5 CVSS v3.1 Published 2024-09-27
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cleartext Storage of Sensitive Information in a Cookie vulnerability in Oceanic Software ValeApp allows Protocol Manipulation, : JSON Hijacking (aka JavaScript Hijacking). This issue affects ValeApp: before v2.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ValeApp before v2.0.0 stores sensitive information in cookies in cleartext (unencrypted), enabling attackers to intercept this data through network sniffing or man-in-the-middle attacks. This vulnerability also facilitates JSON hijacking, where malicious actors can intercept and manipulate JSON responses containing sensitive user data by exploiting the lack of proper security controls on cookie-based data storage.

MitigationUpgrade to ValeApp v2.0.0 or later, which should contain the patch for this vulnerability. As a compensating control, ensure all communication occurs over HTTPS and implement secure cookie attributes (HttpOnly, Secure, SameSite) to prevent client-side access to sensitive cookie data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ValeappApplication
Affected:< 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Valeapp installation and version
    Locate the Valeapp application on your system and check the installed version. Look for version information in the application directory, configuration files, or application metadata. Compare against the affected range: any version before v2.0.0 is vulnerable.
    Affected if The installed Valeapp version is before v2.0.0
  2. Inspect cookies for sensitive data
    Use browser developer tools (Application tab > Cookies) or a network proxy to intercept cookie values. Examine the cookie contents for any sensitive information such as user credentials, session tokens, personal data, or JSON payloads stored in cleartext.
    Affected if Cookies contain unencrypted sensitive data like plaintext passwords, session tokens, or personal information
  3. Check cookie security attributes
    Review the Set-Cookie headers or cookie properties in the browser dev tools. Verify if cookies have the following attributes: Secure (only sent over HTTPS), HttpOnly (not accessible via JavaScript), and SameSite (to prevent CSRF).
    Affected if Cookies lack HttpOnly, Secure, or SameSite attributes, or use SameSite=None without Secure
  4. Verify HTTPS enforcement
    Check if the application forces HTTPS connections. Look for HTTP to HTTPS redirects in the server configuration or application code. Capture network traffic to see if HTTP requests are accepted and if cookies are sent over unencrypted connections.
    Affected if The application accepts HTTP connections or cookies are transmitted over unencrypted channels

You are affected if Valeapp version is before v2.0.0 AND cookies store sensitive data in cleartext without proper security attributes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Upgrade to ValeApp v2.0.0 or later, which should contain the patch for this vulnerability. As a compensating control, ensure all communication occurs over HTTPS and implement secure cookie attributes (HttpOnly, Secure, SameSite) to prevent client-side access to sensitive cookie data.

Recommended fix Moderate confidence

ValeApp v2.0.0

  1. Backup current ValeApp configuration and data
  2. Stop the ValeApp service
  3. Upgrade ValeApp to version 2.0.0 using your package manager or the official upgrade procedure provided by Oceanic Software
  4. Start the ValeApp service
  5. Verify that version 2.0.0 is running correctly
  6. Test that the application functions as expected with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Valeapp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8644 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8644 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data