On this page (7 sections)
Ubuntu has published security notice USN-9058-1 about Action Pack Page Caching. According to the notice, the component incorrectly handled certain request paths when writing cached pages. A remote attacker could possibly use this to write arbitrary files to the web server, and possibly execute arbitrary code.
If you run Ubuntu servers that host web applications, this is worth a quick review. The public information is short, so this article separates what the notice says from what is not confirmed, and lists read-only checks you can run today.
What the notice says
The Ubuntu notice describes one problem: Action Pack Page Caching did not correctly handle certain request paths at the moment it wrote a cached page. Ubuntu words the impact cautiously. A remote attacker could "possibly" write arbitrary files to the web server and "possibly" execute arbitrary code.
The only source available for this story is the Ubuntu notice itself, and only a short summary of it. We have no CVE identifier, CVSS score, list of affected Ubuntu releases, package names or fixed package versions, and no other publisher has independently confirmed or expanded on the details. Open the notice page to get the exact package names, releases and fixed versions before you act.
Background: why request paths matter for caching
Page caching generally means saving a rendered page to disk so the web server can serve it directly later. That requires turning part of the request into a file location. When code that builds a file path from request data does not strictly constrain the result, a write can end up somewhere unintended. That is the general reason path handling bugs around file writes are taken seriously, and why a notice may mention possible code execution.
Whether and how any of that applies to USN-9058-1 depends on details the notice summary does not give. Code execution is described by Ubuntu as a possibility, not a confirmed outcome.
Who is realistically exposed
Based only on the notice, exposure depends on whether the affected Action Pack Page Caching package is installed and in use. The following is our inference, so confirm it against the notice:
- Ubuntu systems where the affected package named in USN-9058-1 is installed, on a release the notice lists.
- Hosting administrators who manage several web applications and may not know which ones use page caching.
- Teams that install libraries through their own dependency tooling instead of Ubuntu packages. A distribution notice covers distribution packages, so check the versions your application actually uses against the notice and the maintainers' guidance.
Applications that do not use page caching are less likely to be affected, but confirm this rather than assume it.
How to check your exposure
Start by finding out whether the package is present. These checks are read-only. First open the notice and note the exact package names, then use them in place of the search terms below if they differ.
On Debian and Ubuntu, this lists installed packages whose name contains "actionpack" or "caching", so you can see whether a related package is present and at which version. Compare the result with the names in the notice:
dpkg -l | grep -i -E 'actionpack|caching'In an application directory that uses Bundler, this searches the dependency files for page caching references. A match means the app declares the component, and the lock file shows the resolved version:
grep -n -i 'page_caching' Gemfile Gemfile.lockTo see which updates are waiting, this lists upgradable packages without installing anything. Look for the package names given in the notice:
apt list --upgradable 2>/dev/null | grep -i -E 'actionpack|caching'What to do now
- Open USN-9058-1 on the Ubuntu site and note the affected packages, releases and fixed versions.
- Check whether any of those packages are installed on your servers, and which applications use them.
- Apply the Ubuntu update for any affected package as soon as it is available for your release.
- For applications that bundle their own copy of the component, update to the fixed release named by Ubuntu or the maintainers, then redeploy.
- Restart the application servers after updating so running processes load the fixed code.
- If you cannot patch immediately, consider turning off page caching for the affected application until you can.
- Review the cache and public directories for files you do not recognize, and check recent web logs for unusual request paths.
- Make sure the application user can write only to the directories it needs, not to code, configuration or web server directories.
On Debian and Ubuntu, once you have confirmed the package name from the notice, upgrade only that package. Replace the placeholder with the exact name listed in USN-9058-1:
sudo apt update && sudo apt install --only-upgrade PACKAGE_NAMEDetection and monitoring afterwards
Because the notice concerns unwanted file writes, the most useful evidence is on disk and in access logs. This search lists requests containing parent-directory or encoded path sequences. Adjust the log location to your setup. Matches are not proof of attack, since scanners probe constantly, but they show whether such requests reached you:
grep -E '\.\./|%2e%2e|%2f%2e' /var/log/nginx/access.log | head -n 50This lists files changed in the last seven days under your application's public directory. Replace the path with your own. Look for unexpected file types, such as scripts, or files outside the folders you normally write to:
find /path/to/app/public -type f -mtime -7 -lsIf you find files you cannot explain, follow Website hacked: what to do and see how to check if a website is hacked. An outside-in view can also help: a read-only security scan of a site you verify can flag exposed content and configuration issues, though it cannot see files written inside your server, as explained in what outside-in malware detection can and cannot see.
What we do not know yet
- Which exact packages and Ubuntu releases are affected, and the fixed versions.
- Whether a CVE identifier has been assigned.
- The severity or CVSS score.
- Whether exploitation has been observed in the wild.
- The precise conditions needed for the file write, and whether code execution is practical in typical configurations.
- Whether other distributions or upstream maintainers have published their own advisories.
We treat these as open until a primary source states them. For other recent coverage, browse the Webforta security blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
