GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
Check your stack
GHSA-xhfx-hgmf-v6vplow

October CMS vulnerable to Potential Host Header Poisoning on misconfigured servers

Impact

When running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning: - https://portswigger.net/web-security/host-header - https://dzone.com/articles/what-is-a-host-header-attack

Source excerpt · OSV
Applies when

If you require assistance with this, please contact your server administrator.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

october/backend Packagist
Affected rangeRecorded fix
Earlier releases before 1.1.2Ecosystem versions1.1.2

Version evidence: OSV · GHSA-xhfx-hgmf-v6vp

View original version evidence (160 explicit versions)

Original source description

Impact

When running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning:

Patches

A feature has been added in v1.1.2 to allow a set of trusted hosts to be specified in the application.

Workarounds

Alternative Workaround

Check to make sure that your web server does not accept any hostname when serving your web application.

  1. Add an entry called testing.tld to your computer's host file and direct it to your server's IP address
  2. Open the address testing.tld in your web browser
  3. Make sure an October CMS website is not available at this address

If an October CMS website is returned, configure your webserver to only allow known hostnames. If you require assistance with this, please contact your server administrator.

References

Reported by Abdullah Hussam

For More Information

If you have any questions or comments about this advisory:

Threat Assessment

<img width="1108" alt="Screen Shot 2021-01-15 at 4 12 57 PM" src="https://user-images.githubusercontent.com/7253840/104783859-92fb3600-574c-11eb-9e21-c0dc05d230a9.png">

References