UBUNTU-CVE-2017-5661: High severity ubuntu/fop vulnerability

Published Apr 18, 2017
·
Updated

In Apache FOP before 2.2, files lying on the filesystem of the server which uses FOP can be revealed to arbitrary users who send maliciously formed SVG files. The file types that can be shown depend on the user context in which the exploitable application is running. If the user is root a full compromise of the server - including confidential or sensitive files - would be possible. XXE can also be used to attack the availability of the server via denial of service as the references within a xml document can trivially trigger an amplification attack.

Affected Software

2 affected componentsFixes available
ubuntu/fop<1:1.1.dfsg-2ubuntu1.1
1:1.1.dfsg-2ubuntu1.1
ubuntu/fop<1:2.1-2ubuntu0.1~esm1
1:2.1-2ubuntu0.1~esm1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/fop to a version that resolves this vulnerability.

    Fixed in 1:1.1.dfsg-2ubuntu1.1
  2. Upgrade

    Upgrade ubuntu/fop to a version that resolves this vulnerability.

    Fixed in 1:2.1-2ubuntu0.1~esm1

Event History

Apr 18, 2017
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who is most exposed to this issue?

Applications that process attacker-supplied SVG files with Apache FOP before 2.2 are exposed. Impact depends on the operating-system permissions of the account running FOP; running it as root can expose sensitive files across the server.

2

What does an attacker need to exploit it?

An attacker needs the ability to submit a maliciously formed SVG file to an application that uses the affected FOP version. The vulnerability requires user interaction according to the supplied severity vector.

3

Are confidentiality and availability both at risk?

Yes. Malicious SVG content can reveal files readable by the FOP process, and XML external entity references can trigger amplification attacks that deny service.

4

What should be prioritized if immediate remediation is not possible?

Prevent untrusted users from submitting SVG files for FOP processing and avoid running the FOP-using application as root. Restricting the process account's filesystem permissions limits which files could be disclosed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203