An issue was discovered in the Linux kernel before 5.1.17. There is a NULL pointer dereference caused by a malicious USB device in the sound/usb/line6/pcm.c driver.

CVE-2019-15221

Improper file verification in Intel® Driver & Support Assistant before 19.7.30.2 may allow an authenticated user to potentially enable escalation of privilege via local access.

**Select Your Region**

Sign In to access restricted content

**Using Intel.com Search**

You can easily search the entire Intel.com site in several ways.

*   Brand Name: **Core i9**
*   Document Number: **123456**
*   Code Name: **Alder Lake**
*   Special Operators: **“Ice Lake”, Ice AND Lake, Ice OR Lake, Ice\***

**Quick Links**

You can also try the quick links below to see results for most popular searches.

*   Product Information
*   Support
*   Drivers & Software

**Recent Searches**

Sign In to access restricted content

**Advanced Search**

**Only search in**

Title Description Content ID

Sign in to access restricted content.

The browser version you are using is not recommended for this site.  
Please consider upgrading to the latest version of your browser by clicking one of the following links.

*   Safari
*   Chrome
*   Edge
*   Firefox

**Intel® Driver & Support Assistant Advisory**

**Summary: **

A potential security vulnerability in Intel® Driver & Support Assistant may allow escalation of privilege.  Intel is releasing software updates to mitigate this potential vulnerability.

**Vulnerability Details:**

CVEID: CVE-2019-11145

Description: Improper directory permissions for Intel® Driver & Support Assistant before 19.7.30.2 may allow an authenticated user to potentially enable escalation of privilege via local access.

CVSS Base Score: 6.7 Medium

CVSS Vector:  CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

CVEID: CVE-2019-11146

Description: Improper file verification in Intel® Driver & Support Assistant before 19.7.30.2 may allow an authenticated user to potentially enable escalation of privilege via local access.

CVSS Base Score: 6.7 Medium

CVSS Vector:  CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

**Affected Products:**

Intel® Driver & Support Assistant before 19.7.30.2.

**Recommendations:**

Intel recommends that users of Intel® Driver & Support Assistant update to 19.7.30.2 or later.

Updates are available for download at this location: https://www.intel.com/content/www/us/en/support/detect.html

**Acknowledgements:**

Intel would like to thank Jakub Palaczynski (CVE-2019-11145) and Eran Shimony (CVE-2019-11146) for reporting these issues.

Intel, and nearly the entire technology industry, follows a disclosure practice called Coordinated Disclosure, under which a cybersecurity vulnerability is generally publicly disclosed only after mitigations are available.

**Revision History**

Revision

Date

Description

1.0

08/13/2019

Initial Release

**Legal Notices and Disclaimers**

Intel provides these materials as-is, with no express or implied warranties.

All products, dates, and figures specified are preliminary based on current expectations, and are subject to change without notice.

Intel products and services described may contain design defects or errors known as errata, which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Intel products that have met their End of Servicing Updates may no longer receive functional and security updates. For additional details on support and servicing, please see this help article. 

Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No product or component can be absolutely secure. Check with your system manufacturer or retailer or learn more at http://intel.com.

Some results have been estimated or simulated using internal Intel analysis or architecture simulation or modeling, and provided to you for informational purposes. Any differences in your system hardware, software or configuration may affect your actual performance.

Intel and the Intel logo are trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

\*Other names and brands may be claimed as the property of others.  

Copyright © Intel Corporation 2022

**Report a Vulnerability**

If you have information about a security issue or vulnerability with an **Intel branded product or technology**, please send an e-mail to secure@intel.com. Encrypt sensitive information using our PGP public key.

Please provide as much information as possible, including:

*   The products and versions affected
*   Detailed description of the vulnerability
*   Information on known exploits

A member of the Intel Product Security Team will review your e-mail and contact you to collaborate on resolving the issue. For more information on how Intel works to resolve security issues, see:

*   Vulnerability handling guidelines

For issues related to Intel's external web presence (Intel.com and related subdomains), please contact Intel's External Security Research team.

**Need product support?**

If you...

*   Have questions about the security features of an Intel product
*   Require technical support
*   Want product updates or patches

  
Please visit Support & Downloads.

*   Report a Vulnerability
*   Product Support

CVE-2019-11145: INTEL-SA-00276

xtrlock through 2.10 does not block multitouch events. Consequently, an attacker at a locked screen can send input to (and thus control) various programs such as Chromium via events such as pan scrolling, "pinch and zoom" gestures, or even regular mouse clicks (by depressing the touchpad once and then clicking with a different finger).

CVE-2016-10894: #830726 - xtrlock: CVE-2016-10894: xtrlock does not block multitouch events

The FV Flowplayer Video Player plugin before 7.3.14.727 for WordPress allows email subscription XSS.

CVE-2019-14799: FV Flowplayer Video Player

ImageMagick 7.0.8-50 Q16 has a heap-based buffer over-read at MagickCore/pixel-accessor.h in GetPixelChannel.

There's a heap-buffer-overflow at MagickCore/pixel-accessor.h:116:10 in GetPixelChannel.

run\_cmd:  
magick -seed 0 "(" magick:netscape -monochrome  ")" "(" magick:netscape +repage ")" -geometry 433%-80-57 -adjoin -evaluate-sequence Median   tmp

Here's ASAN log.

    ==30168==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7febb7ba1400 at pc 0x7febc5808632 bp 0x7ffd269baff0 sp 0x7ffd269bafe8
    READ of size 4 at 0x7febb7ba1400 thread T0
        #0 0x7febc5808631 in GetPixelChannel ./MagickCore/pixel-accessor.h:116:10
        #1 0x7febc5805ff6 in EvaluateImages MagickCore/statistic.c:587:33
        #2 0x7febc4e1a5bf in CLIListOperatorImages MagickWand/operation.c:4084:22
        #3 0x7febc4e2435e in CLIOption MagickWand/operation.c:5279:14
        #4 0x7febc4c65a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7
        #5 0x7febc4c66d0a in MagickImageCommand MagickWand/magick-cli.c:796:5
        #6 0x7febc4cb0ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14
        #7 0x526f95 in MagickMain utilities/magick.c:149:10
        #8 0x5268e1 in main utilities/magick.c:180:10
        #9 0x7febbf727b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
        #10 0x41b069 in _start (install/bin/magick+0x41b069)
    
    0x7febb7ba1400 is located 0 bytes to the right of 248832-byte region [0x7febb7b64800,0x7febb7ba1400)
    allocated by thread T0 here:
        #0 0x4e6200 in __interceptor_posix_memalign (install/bin/magick+0x4e6200)
        #1 0x7febc569fed6 in AcquireAlignedMemory MagickCore/memory.c:265:7
        #2 0x7febc53e861c in OpenPixelCache MagickCore/cache.c:3728:46
        #3 0x7febc53ee901 in GetImagePixelCache MagickCore/cache.c:1754:18
        #4 0x7febc53f4bc9 in SyncImagePixelCache MagickCore/cache.c:5488:28
        #5 0x7febc5653831 in SetImageStorageClass MagickCore/image.c:2627:10
        #6 0x7febc54187e2 in AcquireImageColormap MagickCore/colormap.c:144:10
        #7 0x7febc575d137 in AssignImageColors MagickCore/quantize.c:514:7
        #8 0x7febc5753f38 in QuantizeImage MagickCore/quantize.c:2724:14
        #9 0x7febc53ae56c in SetImageType MagickCore/attribute.c:1495:14
        #10 0x7febc4e0cace in CLISimpleOperatorImage MagickWand/operation.c:2792:18
        #11 0x7febc4dfec78 in CLISimpleOperatorImages MagickWand/operation.c:3685:12
        #12 0x7febc4e24315 in CLIOption MagickWand/operation.c:5273:16
        #13 0x7febc4c65a99 in ProcessCommandOptions MagickWand/magick-cli.c:477:7
        #14 0x7febc4c66d0a in MagickImageCommand MagickWand/magick-cli.c:796:5
        #15 0x7febc4cb0ba1 in MagickCommandGenesis MagickWand/mogrify.c:185:14
        #16 0x526f95 in MagickMain utilities/magick.c:149:10
        #17 0x5268e1 in main utilities/magick.c:180:10
        #18 0x7febbf727b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
    
    SUMMARY: AddressSanitizer: heap-buffer-overflow ./MagickCore/pixel-accessor.h:116:10 in GetPixelChannel

CVE-2019-13299: heap-buffer-overflow at MagickCore/pixel-accessor.h:116:10 in GetPixelChannel · Issue #1610 · ImageMagick/ImageMagick

Incorect derivation of a packet length in WebRTC in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to potentially exploit heap corruption via a crafted video file.

**Chrome Releases**

Release updates from the Chrome team

CVE-2018-6156: Stable Channel Update for Desktop

Use after free in V8 in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

CVE-2019-5813

Object lifetime issue in V8 in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

CVE-2019-5807

Object lifetime issue in Blink in Google Chrome prior to 72.0.3626.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.

CVE-2019-5786

Inappropriate implementation in Blink in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to bypass same origin policy via a crafted HTML page.

Tag

#chrome