dbcve.org
AroraApplication · Arora Browser

CVE-2011-3367

MEDIUM · 5.0 CVSS v2.0 Published 2011-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
Arora, possibly 0.11 and other versions, does not use a certain font when rendering certificate fields in a security dialog, which allows remote attackers to spoof the common name (CN) of a certificate via rich text.

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

The Arora web browser (versions 0.11 and possibly others) fails to use a specific font when rendering certificate fields in the security dialog. This allows remote attackers to spoof the certificate's Common Name (CN) by using rich text characters that appear different due to inconsistent font rendering in the certificate validation UI.

MitigationUpdate Arora to a patched version if available, or migrate to a maintained browser that properly handles certificate field rendering with consistent fonts.

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
AroraApplication
Affected:= 0.11.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
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/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. Confirm Arora browser is installed
    Search for the Arora executable on the system (common locations: C:\Program Files\Arora\arora.exe on Windows, /usr/bin/arora or /Applications/Arora.app on Unix-like systems)
    Affected if Arora browser is present on the system
  2. Identify installed Arora version
    Run 'arora --version' from command line, or right-click the arora.exe file and view Properties > Details to find the File Version
    Affected if Version is 0.11.0 or an unpatched variant of 0.11.x
  3. Verify certificate dialog rendering behavior
    Navigate to any HTTPS website in Arora, click the lock icon in address bar, then View Certificate - examine how the Common Name (CN) field is displayed
    Affected if The CN field displays characters using inconsistent fonts or renders international/Unicode characters without proper handling, allowing confusable characters to appear as legitimate ASCII

If Arora version 0.11.0 is installed and displays certificate CN fields with inconsistent font rendering, the environment is vulnerable to IDN homograph spoofing in the certificate validation UI.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Arora to a patched version if available, or migrate to a maintained browser that properly handles certificate field rendering with consistent fonts.

Fix this in Arora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3367 — 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-2011-3367 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