GraniApplication · Fenrir

CVE-2010-3919

MEDIUM · 5.8 CVSS v2.0 Published 2010-12-10
Fix available
A fix is available. Upgrade to after 4.5 or later.
See remediation →
67/100
Remediation priority · Elevated
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
Fenrir Grani 4.5 and earlier does not prevent interaction between web script and the clipboard, which allows remote attackers to read or modify the clipboard contents via a crafted web site.

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 · high confidence

Fenrir Grani 4.5 and earlier fails to restrict web script access to the system clipboard, allowing any crafted website to read or modify clipboard contents. This is a cross-origin clipboard access vulnerability where the application does not enforce proper Same-Origin Policy (SOP) restrictions on clipboard operations.

MitigationUpgrade to Fenrir Grani version 4.6 or later which implements proper clipboard access controls. As an interim measure, disable JavaScript execution or use a browser extension that blocks clipboard access by untrusted web origins.

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
GraniApplication
Affected:<= 4.5= 3.0= 3.1= 3.2= 3.5= 4.0= 4.1= 4.2= 4.3= 4.4

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/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 installed Fenrir Grani version
    Check the application's 'About' dialog, help menu, or documentation for the version number. Alternatively, look for version information in the application installation directory or registry entries.
    Affected if The version is 4.5 or any of the listed affected versions (3.0, 3.1, 3.2, 3.5, 4.0, 4.1, 4.2, 4.3, 4.4). Compare your installed version to the affected ranges provided.
  2. Confirm web scripting interface is enabled
    Check the application settings or configuration options for any web-based interface, HTML viewer, or scripting feature that renders or executes web content.
    Affected if The application exposes a web interface or scripting feature that loads external or untrusted web content.
  3. Verify clipboard access from web content
    Test whether a webpage loaded within the application can access the system clipboard using standard browser clipboard APIs (e.g., navigator.clipboard, document.execCommand with clipboard operations).
    Affected if Web content loaded in the application can read or modify clipboard contents without user consent or origin restrictions.
  4. Check Same-Origin Policy enforcement
    Load a webpage from one origin (domain) and attempt to access clipboard data from a different origin within the application to test cross-origin restrictions.
    Affected if The application allows cross-origin clipboard access without enforcing Same-Origin Policy restrictions.

You are affected if you are running Fenrir Grani version 4.5 or earlier and the application has a web interface or scripting feature that is enabled, allowing web content to access the system clipboard without proper origin restrictions.

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.

From vendor data
Upgrade available Upgrade to a release after 4.5
Interim mitigation

Upgrade to Fenrir Grani version 4.6 or later which implements proper clipboard access controls. As an interim measure, disable JavaScript execution or use a browser extension that blocks clipboard access by untrusted web origins.

Fix this in Grani Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2010-3919 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