CVE-2016-3619

Reference Links

• https://support.apple.com/en-us/HT207617 (Advisory)
• http://bugzilla.maptools.org/show_bug.cgi?id=2567
• http://www.openwall.com/lists/oss-security/2016/04/07/1
• http://www.securityfocus.com/bid/85919
• http://www.securitytracker.com/id/1035508
• https://security.gentoo.org/glsa/201701-16

Parent vulnerabilities

(Appears in the following advisories)

• HT207617

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2017-2397
• CVE-2017-2430
• CVE-2017-2462
• CVE-2017-2379
• CVE-2017-2417
• CVE-2017-2444
• CVE-2017-2435
• CVE-2017-2450
• CVE-2017-2461
• CVE-2017-2414
• CVE-2017-2487
• CVE-2017-2406
• CVE-2017-2407
• CVE-2017-2439
• CVE-2017-2434
• CVE-2017-2428
• CVE-2017-2416
• CVE-2017-2432
• CVE-2017-2467
• CVE-2016-3619
• CVE-2017-2412
• CVE-2017-2491
• CVE-2017-2492
• CVE-2017-2398
• CVE-2017-2401
• CVE-2017-2440
• CVE-2017-2456
• CVE-2017-2472
• CVE-2017-2473
• CVE-2017-2474
• CVE-2017-2478
• CVE-2017-2482
• CVE-2017-2483
• CVE-2017-2490
• CVE-2017-2458
• CVE-2017-2448
• CVE-2017-2390
• CVE-2017-2441
• CVE-2017-5029
• CVE-2017-2399
• CVE-2017-2484
• CVE-2017-2380
• CVE-2017-2404
• CVE-2017-2376
• CVE-2017-2384
• CVE-2017-2389
• CVE-2017-2453
• CVE-2017-2393
• CVE-2017-2400
• CVE-2017-6976
• CVE-2017-2423
• CVE-2017-2451
• CVE-2017-2485
• CVE-2017-2452
• CVE-2017-2378
• CVE-2017-2486
• CVE-2017-2386
• CVE-2017-2394
• CVE-2017-2396
• CVE-2016-9642
• CVE-2017-2395
• CVE-2017-2454
• CVE-2017-2455
• CVE-2017-2457
• CVE-2017-2459
• CVE-2017-2460
• CVE-2017-2464
• CVE-2017-2465
• CVE-2017-2466
• CVE-2017-2468
• CVE-2017-2469
• CVE-2017-2470
• CVE-2017-2476
• CVE-2017-2481
• CVE-2017-2415
• CVE-2017-2419
• CVE-2016-9643
• CVE-2017-2424
• CVE-2017-2433
• CVE-2017-2364
• CVE-2017-2367
• CVE-2017-2445
• CVE-2017-2446
• CVE-2017-2447
• CVE-2017-2463
• CVE-2017-2471
• CVE-2017-2475
• CVE-2017-2479
• CVE-2017-2480
• CVE-2017-2493
• CVE-2017-2442
• CVE-2017-2377
• CVE-2017-2405

Frequently Asked Questions

• What is the severity of CVE-2016-3619?

  CVE-2016-3619 is considered a medium severity vulnerability due to its potential for causing information disclosure.

• How do I fix CVE-2016-3619?

  To fix CVE-2016-3619, users should update LibTIFF to version 4.0.7 or later.

• What software is affected by CVE-2016-3619?

  CVE-2016-3619 affects LibTIFF versions 4.0.6 and earlier, and Apple iOS versions prior to 10.3.

• What impact does CVE-2016-3619 have on my system?

  CVE-2016-3619 can lead to out-of-bounds read vulnerabilities which may allow remote attackers to access sensitive information.

• Who is the vendor that addressed CVE-2016-3619?

  Apple is the vendor that addressed CVE-2016-3619 by updating the LibTIFF version used in iOS.