Skip to content
Noroxi
CVE-2009-3895· NVD / CVE Program· CNA redhat

Heap-based buffer overflow in the exif_entry_fix function (aka the tag fixup routine) in libexif/exif-entry.c in libexif 0.6.18 allows remot

Noroxi assessment

Priority: Monitor (action score 29/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 5.1% (FIRST EPSS); higher than 92.4% of all records.
  • Fixed version: libexif (Alpine:v3.10) 0.6.19-r0; libexif (Debian:12) 0.6.19-1.

Low priority for now. Upgrade to libexif (Alpine:v3.10) 0.6.19-r0; libexif (Debian:12) 0.6.19-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Heap-based buffer overflow in the exif_entry_fix function (aka the tag fixup routine) in libexif/exif-entry.c in libexif 0.6.18 allows remote attackers to cause a denial of service or possibly execute arbitrary code via an invalid EXIF image. NOTE: some of these details are obtained from third party information.

MediumCVSS 6.8 · v2.0—No exploit Fix available
Published
Nov 20, 2009
Updated
Jun 16, 2026
EPSS
5.1% · 92th percentile

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2009-3895

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for libexif project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
libexif projectlibexif

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • libexif project libexif0.6.18

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10libexifbefore 0.6.19-r00.6.19-r0
Debian:12libexifbefore 0.6.19-10.6.19-1

Same product

libexif project: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-13112An issue was discovered in libexif before 0.6.22.
    37Monitor
  • CVE-2017-7544libexif through 0.6.21 is vulnerable to out-of-bounds heap read vulnerability in exif_data_save_data_entry function in libexif/exif-data.c c
    37Monitor
  • CVE-2020-13113An issue was discovered in libexif before 0.6.22.
    33Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2007-6351Dec 19, 2007 · libexif 0.6.16 and earlier allows context-dependent attackers to cause a denial of service (infinite recursion) via an image file with craft
    18Monitor
  • Later →CVE-2012-2812Jul 13, 2012 · The exif_entry_get_value function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) before 0.6.21 allows remote attackers to cau
    26Monitor
  • Later →CVE-2012-2813Jul 13, 2012 · The exif_convert_utf16_to_utf8 function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) before 0.6.21 allows remote attackers
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:libexif0.6.19-r0 · Alpine:v3.10Package registry (OSV)
debian:libexif0.6.19-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    P

    Weakness class (CWE)

    CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

    CVSS vector

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

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    ATT&CK techniques

    —

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    Show all references (9 more)

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records