Erdas Er ViewerApplication · Hexagon

CVE-2013-3483

HIGH · 9.3 CVSS v2.0 Published 2014-01-19
Fix available
A fix is available. Upgrade to after 13.0.1.1298 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Stack-based buffer overflow in ermapper_u.dll in Intergraph ERDAS ER Viewer before 13.0.1.1301 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted ERS file.

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

Stack-based buffer overflow in the ermapper_u.dll library of Intergraph ERDAS ER Viewer allows remote attackers to execute arbitrary code by supplying a specially crafted ERS file. The vulnerability stems from insufficient bounds checking during ERS file parsing, enabling an attacker to overwrite stack memory and redirect execution flow.

MitigationUpdate ERDAS ER Viewer to version 13.0.1.1301 or later to obtain the vendor patch. Until patched, avoid opening untrusted ERS files from unknown sources.

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
Erdas Er ViewerApplication
Affected:<= 13.0.1.1298= 11.04= 13.00.0001

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Verify ERDAS ER Viewer installation
    Locate the ERDAS ER Viewer application on the system, typically found in Program Files or Program Files (x86) directories under the Hexagon or ERDAS folder
    Affected if The application is installed and present on the system
  2. Check installed version number
    Right-click the ERDAS ER Viewer executable, select Properties, and view the Version tab; or open the application and check About/Help menu for version information
    Affected if The version is 13.0.1.1298 or lower, equals 11.04, or equals 13.00.0001
  3. Verify ermapper_u.dll presence
    Search for the ermapper_u.dll file within the ERDAS ER Viewer installation directory
    Affected if The ermapper_u.dll library exists in the application folder, indicating the vulnerable component is present
  4. Confirm ERS file processing capability
    Check if the application is configured to handle .ers file extensions or if users routinely open ERS files
    Affected if ERS file handling is enabled or users open ERS files using this viewer

A system is affected if ERDAS ER Viewer version 13.0.1.1298 or earlier, 11.04, or 13.00.0001 is installed and the application processes ERS files, as the buffer overflow in ermapper_u.dll will trigger upon parsing a specially crafted ERS file.

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 a release after 13.0.1.1298
Interim mitigation

Update ERDAS ER Viewer to version 13.0.1.1301 or later to obtain the vendor patch. Until patched, avoid opening untrusted ERS files from unknown sources.

Recommended fix High confidence

13.0.1.1301

  1. Download Erdas ER Viewer version 13.0.1.1301 or later from the official Intergraph/ERDAS website
  2. Install the updated version of Erdas ER Viewer
  3. Verify the installation by checking Help > About for version 13.0.1.1301 or higher

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

Fix this in Erdas Er Viewer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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