According to the versions of the ghostscript package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - It was discovered that the ghostscript .tempfile     function did not properly handle file permissions. An     attacker could possibly exploit this to exploit this to     bypass the -dSAFER protection and delete files or     disclose their content via a specially crafted     PostScript document.i1/4^CVE-2018-15908i1/4%0

  - It was discovered that the ghostscript .shfill operator     did not properly validate certain types. An attacker     could possibly exploit this to bypass the -dSAFER     protection and crash ghostscript or, possibly, execute     arbitrary code in the ghostscript context via a     specially crafted PostScript     document.i1/4^CVE-2018-15909i1/4%0

  - It was discovered that ghostscript did not properly     verify the key used in aesdecode. An attacker could     possibly exploit this to bypass the -dSAFER protection     and crash ghostscript or, possibly, execute arbitrary     code in the ghostscript context via a specially crafted     PostScript document.i1/4^CVE-2018-15911i1/4%0

  - It was discovered that the ghostscript .type operator     did not properly validate its operands. A specially     crafted PostScript document could exploit this to crash     ghostscript or, possibly, execute arbitrary code in the     context of the ghostscript process.i1/4^CVE-2018-16511i1/4%0

  - It was discovered that the ghostscript did not properly     restrict access to files open prior to enabling the
    -dSAFER mode. An attacker could possibly exploit this     to bypass the -dSAFER protection and disclose the     content of affected files via a specially crafted     PostScript document.i1/4^CVE-2018-16539i1/4%0

  - It was discovered that the ghostscript device cleanup     did not properly handle devices replaced with a null     device. An attacker could possibly exploit this to     bypass the -dSAFER protection and crash ghostscript or,     possibly, execute arbitrary code in the ghostscript     context via a specially crafted PostScript     document.i1/4^CVE-2018-16541i1/4%0

  - An issue was discovered in Artifex Ghostscript before     9.25. Incorrect 'restoration of privilege' checking     when running out of stack during exception handling     could be used by attackers able to supply crafted     PostScript to execute code using the 'pipe'     instruction. This is due to an incomplete fix for     CVE-2018-16509.i1/4^CVE-2018-16802i1/4%0

  - It was found that RHSA-2018:2918 did not fully fix     CVE-2018-16509. An attacker could possibly exploit     another variant of the flaw and bypass the -dSAFER     protection to, for example, execute arbitrary shell     commands via a specially crafted PostScript     document.i1/4^CVE-2018-16863i1/4%0

  - Artifex Ghostscript before 9.25 allowed a user-writable     error exception table, which could be used by remote     attackers able to supply crafted PostScript to     potentially overwrite or replace error handlers to     inject code.i1/4^CVE-2018-17183i1/4%0

  - Artifex Ghostscript 9.25 and earlier allows attackers     to bypass a sandbox protection mechanism via vectors     involving errorhandler setup. NOTE: this issue exists     because of an incomplete fix for     CVE-2018-17183.i1/4^CVE-2018-17961i1/4%0

  - Artifex Ghostscript allows attackers to bypass a     sandbox protection mechanism by leveraging exposure of     system operators in the saved execution stack in an     error object.i1/4^CVE-2018-18073i1/4%0

  - Artifex Ghostscript 9.25 and earlier allows attackers     to bypass a sandbox protection mechanism via vectors     involving the 1Policy operator.i1/4^CVE-2018-18284i1/4%0

  - In Artifex Ghostscript through 9.25, the setpattern     operator did not properly validate certain types. A     specially crafted PostScript document could exploit     this to crash Ghostscript or, possibly, execute     arbitrary code in the context of the Ghostscript     process. This is a type confusion issue because of     failure to check whether the Implementation of a     pattern dictionary was a structure     type.i1/4^CVE-2018-19134i1/4%0

  - An issue was discovered in Artifex Ghostscript before     9.26. LockSafetyParams is not checked correctly if     another device is used.i1/4^CVE-2018-19409i1/4%0

  - It was discovered that ghostscript did not properly     handle certain stack overflow error conditions. An     attacker could possibly exploit this to bypass the
    -dSAFER protection and crash ghostscript or, possibly,     execute arbitrary code in the ghostscript context via a     specially crafted PostScript     document.i1/4^CVE-2018-16542i1/4%0

  - It was discovered that the type of the     LockDistillerParams parameter is not properly verified.
    An attacker could possibly exploit this to bypass the
    -dSAFER protection and crash ghostscript or, possibly,     execute arbitrary code in the ghostscript context via a     specially crafted PostScript     document.i1/4^CVE-2018-15910i1/4%0

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the versions of the ghostscript package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - It was discovered that the ghostscript .tempfile     function did not properly handle file permissions. An     attacker could possibly exploit this to exploit this to     bypass the -dSAFER protection and delete files or     disclose their content via a specially crafted     PostScript document.i1/4^CVE-2018-15908i1/4%0

  - It was discovered that the ghostscript .shfill operator     did not properly validate certain types. An attacker     could possibly exploit this to bypass the -dSAFER     protection and crash ghostscript or, possibly, execute     arbitrary code in the ghostscript context via a     specially crafted PostScript     document.i1/4^CVE-2018-15909i1/4%0

  - It was discovered that ghostscript did not properly     verify the key used in aesdecode. An attacker could     possibly exploit this to bypass the -dSAFER protection     and crash ghostscript or, possibly, execute arbitrary     code in the ghostscript context via a specially crafted     PostScript document.i1/4^CVE-2018-15911i1/4%0

  - It was discovered that the ghostscript .type operator     did not properly validate its operands. A specially     crafted PostScript document could exploit this to crash     ghostscript or, possibly, execute arbitrary code in the     context of the ghostscript process.i1/4^CVE-2018-16511i1/4%0

  - It was discovered that the ghostscript did not properly     restrict access to files open prior to enabling the
    -dSAFER mode. An attacker could possibly exploit this     to bypass the -dSAFER protection and disclose the     content of affected files via a specially crafted     PostScript document.i1/4^CVE-2018-16539i1/4%0

  - It was discovered that the ghostscript device cleanup     did not properly handle devices replaced with a null     device. An attacker could possibly exploit this to     bypass the -dSAFER protection and crash ghostscript or,     possibly, execute arbitrary code in the ghostscript     context via a specially crafted PostScript     document.i1/4^CVE-2018-16541i1/4%0

  - An issue was discovered in Artifex Ghostscript before     9.25. Incorrect 'restoration of privilege' checking     when running out of stack during exception handling     could be used by attackers able to supply crafted     PostScript to execute code using the 'pipe'     instruction. This is due to an incomplete fix for     CVE-2018-16509.i1/4^CVE-2018-16802i1/4%0

  - It was found that RHSA-2018:2918 did not fully fix     CVE-2018-16509. An attacker could possibly exploit     another variant of the flaw and bypass the -dSAFER     protection to, for example, execute arbitrary shell     commands via a specially crafted PostScript     document.i1/4^CVE-2018-16863i1/4%0

  - Artifex Ghostscript before 9.25 allowed a user-writable     error exception table, which could be used by remote     attackers able to supply crafted PostScript to     potentially overwrite or replace error handlers to     inject code.i1/4^CVE-2018-17183i1/4%0

  - Artifex Ghostscript 9.25 and earlier allows attackers     to bypass a sandbox protection mechanism via vectors     involving errorhandler setup. NOTE: this issue exists     because of an incomplete fix for     CVE-2018-17183.i1/4^CVE-2018-17961i1/4%0

  - Artifex Ghostscript allows attackers to bypass a     sandbox protection mechanism by leveraging exposure of     system operators in the saved execution stack in an     error object.i1/4^CVE-2018-18073i1/4%0

  - Artifex Ghostscript 9.25 and earlier allows attackers     to bypass a sandbox protection mechanism via vectors     involving the 1Policy operator.i1/4^CVE-2018-18284i1/4%0

  - In Artifex Ghostscript through 9.25, the setpattern     operator did not properly validate certain types. A     specially crafted PostScript document could exploit     this to crash Ghostscript or, possibly, execute     arbitrary code in the context of the Ghostscript     process. This is a type confusion issue because of     failure to check whether the Implementation of a     pattern dictionary was a structure     type.i1/4^CVE-2018-19134i1/4%0

  - An issue was discovered in Artifex Ghostscript before     9.26. LockSafetyParams is not checked correctly if     another device is used.i1/4^CVE-2018-19409i1/4%0

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The version of ghostscript installed on the remote host is prior to 9.25-5. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2021-1598 advisory.

    Artifex Ghostscript before 9.25 allowed a user-writable error exception table, which could be used by     remote attackers able to supply crafted PostScript to potentially overwrite or replace error handlers to     inject code. (CVE-2018-17183)

    Artifex Ghostscript 9.25 and earlier allows attackers to bypass a sandbox protection mechanism via vectors     involving errorhandler setup. NOTE: this issue exists because of an incomplete fix forCVE-2018-17183.
    (CVE-2018-17961)

    Artifex Ghostscript allows attackers to bypass a sandbox protection mechanism by leveraging exposure of     system operators in the saved execution stack in an error object. (CVE-2018-18073)

    Artifex Ghostscript 9.25 and earlier allows attackers to bypass a sandbox protection mechanism via vectors     involving the 1Policy operator. (CVE-2018-18284)

    In Artifex Ghostscript through 9.25, the setpattern operator did not properly validate certain types. A     specially crafted PostScript document could exploit this to crash Ghostscript or, possibly, execute     arbitrary code in the context of the Ghostscript process. This is a type confusion issue because of     failure to check whether the Implementation of a pattern dictionary was a structure type. (CVE-2018-19134)

    An issue was discovered in Artifex Ghostscript before 9.26. LockSafetyParams is not checked correctly if     another device is used. (CVE-2018-19409)

    psi/zdevice2.c in Artifex Ghostscript before 9.26 allows remote attackers to bypass intended access     restrictions because available stack space is not checked when the device remains the same.
    (CVE-2018-19475)

    psi/zicc.c in Artifex Ghostscript before 9.26 allows remote attackers to bypass intended access     restrictions because of a setcolorspace type confusion. (CVE-2018-19476)

    psi/zfjbig2.c in Artifex Ghostscript before 9.26 allows remote attackers to bypass intended access     restrictions because of a JBIG2Decode type confusion. (CVE-2018-19477)

    A flaw was found in the .pdf_hook_DSC_Creator procedure where it did not properly secure its privileged     calls, enabling scripts to bypass `-dSAFER` restrictions. A specially crafted PostScript file could     disable security protection and then have access to the file system, or execute arbitrary commands.
    (CVE-2019-14811)

    A flaw was found in the .setuserparams2 procedure where it did not properly secure its privileged calls,     enabling scripts to bypass `-dSAFER` restrictions. A specially crafted PostScript file could disable     security protection and then have access to the file system, or execute arbitrary commands.
    (CVE-2019-14812)

    A flaw was found in the setsystemparams procedure where it did not properly secure its privileged calls,     enabling scripts to bypass `-dSAFER` restrictions. A specially crafted PostScript file could disable     security protection and then have access to the file system, or execute arbitrary commands.
    (CVE-2019-14813)

    A flaw was found in the .pdfexectoken and other procedures where it did not properly secure its privileged     calls, enabling scripts to bypass `-dSAFER` restrictions. A specially crafted PostScript file could     disable security protection and then have access to the file system, or execute arbitrary commands.
    (CVE-2019-14817)

    A flaw was found in the `.charkeys` procedure, where it did not properly secure its privileged calls,     enabling scripts to bypass `-dSAFER` restrictions. An attacker could abuse this flaw by creating a     specially crafted PostScript file that could escalate privileges within the Ghostscript and access files     outside of restricted areas or execute commands. (CVE-2019-14869)

    It was found that the superexec operator was available in the internal dictionary.  A specially crafted     PostScript file could use this flaw in order to, for example, have access to the file system outside of     the constrains imposed by -dSAFER. (CVE-2019-3835)

    It was found that the forceput operator could be extracted from the DefineResource method. A specially     crafted PostScript file could use this flaw in order to, for example, have access to the file system     outside of the constrains imposed by -dSAFER. (CVE-2019-3838)

    It was found that some privileged operators remained accessible from various places after     theCVE-2019-6116fix. A specially crafted PostScript file could use this flaw in order to, for example,     have access to the file system outside of the constrains imposed by -dSAFER. (CVE-2019-3839)

    It was found that ghostscript could leak sensitive operators on the operand stack when a pseudo-operator     pushes a subroutine. A specially crafted PostScript file could use this flaw to escape the -dSAFER     protection in order to, for example, have access to the file system outside of the SAFER constraints.
    (CVE-2019-6116)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
121276	EulerOS Virtualization 2.5.1 : ghostscript (EulerOS-SA-2019-1016)	Nessus	Huawei Local Security Checks	2019/1/22	2022/5/24	critical
123891	EulerOS Virtualization 2.5.3 : ghostscript (EulerOS-SA-2019-1205)	Nessus	Huawei Local Security Checks	2019/4/9	2022/5/20	critical
146633	Amazon Linux 2 : ghostscript (ALAS-2021-1598)	Nessus	Amazon Linux Local Security Checks	2021/2/19	2024/12/11	critical

検出

プラグインの検索

critical

critical

critical