CodeSampleX

Sample

rack-protection 4.2.1: Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion.

Verified sample for gem rack-protection 4.2.1: Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on…

sha256:211d7395fda74de66490b727f70e99004de2ff33d235445d7c9a625f290745c2

This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people. MIT-0

Execution evidence

The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.

Evidence basis
Signed contract pass
Verification receipts
2
Signing keys that built it
1
Declared environment ruby linux x64 ruby ruby rubygems

Verification-run environments

Environment Contract Stages Run
ruby 3 · linux alpine/x64 · docker ed25519:d91480838ac982c9 PASS compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS
CONTAINER_RUN · rubygems@1
2026-08-16
ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 SKIPPED compile:SKIPPED · contract:SKIPPED · load:SKIPPED · resolve:FAIL
CONTAINER_RUN · rubygems@1
2026-08-18

Case

HOW
Goal
Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion.
Packages
Symbols
  • Rack::Protection
  • Rack::Protection::SessionHijacking
Environment
ruby
Created
2026-08-16T16:38:09Z

Contract

  1. Rack::Protection.new with default options retains session payload and omits tracking state across requests with altered user agents, leaving session hijacking defense disabled until session_hijacking is explicitly passed via use.
  2. Passing use: :session_hijacking to Rack::Protection.new tracks user agent headers in session tracking state and drops the session when the user agent changes on subsequent requests.

Files

  • Gemfile
  • NOTES.md
  • csx.json
  • test/contract.rb

Download the source artifact (tar.gz)

Source

Gemfile
source "https://rubygems.org"

gem "rack-protection", "4.2.1"
NOTES.md
# Session Hijacking Protection in Rack::Protection 4.x

A search of known solutions returned existing entries for header name casing in `Rack::Protection::XSSHeader` and token validation in `Rack::Protection::AuthenticityToken`. This sample targets a different trap: the change to default middleware inclusion for `Rack::Protection::SessionHijacking` in version 4.x.

In `rack-protection` 3.x, `Rack::Protection.new(app)` automatically included `SessionHijacking` in the default protection stack, clearing the session if a client altered its `HTTP_USER_AGENT`. In 4.x, `SessionHijacking` is disabled by default and requires explicit opt-in via `use: :session_hijacking`.

When expecting 3.x behavior under 4.x, the failure is silent with a green build: requests with spoofed or altered user-agent headers retain existing session data rather than having the session cleared.
csx.json
{"case":{"believed":"Initializing Rack::Protection with default options includes session hijacking defense that clears the session when a client user-agent header changes.","caseId":"case:sha256:4cc1bcdb7a5ae40e6e865bdd9147fef818fcbb2093cb9242ee4492a49fb6d9cc","contract":["Rack::Protection.new with default options retains session payload and omits tracking state across requests with altered user agents, leaving session hijacking defense disabled until session_hijacking is explicitly passed via use.","Passing use: :session_hijacking to Rack::Protection.new tracks user agent headers in session tracking state and drops the session when the user agent changes on subsequent requests."],"goal":"Require explicit opt-in to enable session hijacking protection in Rack::Protection 4.x rather than relying on default middleware inclusion.","kind":"HOW","packages":["pkg:gem/rack-protection@4.2.1"],"schemaVersion":1,"symbols":["Rack::Protection","Rack::Protection::SessionHijacking"]},"contractCommand":["ruby","test/contract.rb"],"environment":{"arch":"x64","ecosystem":"gem","executionContext":"ruby","language":"ruby","os":"linux","packageManager":"rubygems","runtime":"ruby","schemaVersion":1},"license":"MIT-0","packages":["pkg:gem/rack-protection@4.2.1"],"schemaVersion":1,"symbols":["Rack::Protection","Rack::Protection::SessionHijacking"],"verifierAdapter":"rubygems@1"}
test/contract.rb
# frozen_string_literal: true

require "stringio"
require "rack/protection"

class DummyApp
  def call(_env)
    [200, { "content-type" => "text/plain" }, ["ok"]]
  end
end

def make_env(session, user_agent)
  {
    "REQUEST_METHOD" => "GET",
    "SCRIPT_NAME" => "",
    "PATH_INFO" => "/",
    "QUERY_STRING" => "",
    "rack.url_scheme" => "http",
    "SERVER_NAME" => "example.com",
    "SERVER_PORT" => "80",
    "rack.input" => StringIO.new(""),
    "HTTP_USER_AGENT" => user_agent,
    "rack.session" => session
  }
end

# 1. Default Rack::Protection stack in 4.x disables SessionHijacking by default
default_app = Rack::Protection.new(DummyApp.new)
session_default = { "auth_token" => "secret-token-xyz" }

status1, _, body1 = default_app.call(make_env(session_default, "Mozilla/5.0 (Windows NT 10.0)"))
body1.close if body1.respond_to?(:close)
unless status1 == 200
  warn "Expected HTTP 200 on initial request, got #{status1}"
  exit 1
end

# Changing User-Agent on subsequent request under default protection does NOT drop the session in 4.x
status2, _, body2 = default_app.call(make_env(session_default, "curl/8.4.0"))
body2.close if body2.respond_to?(:close)
unless status2 == 200
  warn "Expected HTTP 200 on second request, got #{status2}"
  exit 1
end

unless session_default["auth_token"] == "secret-token-xyz"
  warn "Expected default Rack::Protection to preserve session on User-Agent change in 4.x"
  exit 1
end

if session_default.key?(:tracking)
  warn "Expected default Rack::Protection not to populate tracking state when session_hijacking is omitted"
  exit 1
end

# 2. SessionHijacking must be explicitly opted into via `use: :session_hijacking`
opt_in_app = Rack::Protection.new(DummyApp.new, use: :session_hijacking)
session_opt_in = { "auth_token" => "secret-token-xyz" }

status3, _, body3 = opt_in_app.call(make_env(session_opt_in, "Mozilla/5.0 (Windows NT 10.0)"))
body3.close if body3.respond_to?(:close)
unless status3 == 200
  warn "Expected HTTP 200 with session_hijacking enabled, got #{status3}"
  exit 1
end

unless session_opt_in.key?(:tracking)
  warn "Expected explicit session_hijacking to track request headers in session"
  exit 1
end

# Changing User-Agent with session_hijacking explicitly enabled triggers drop_session
status4, _, body4 = opt_in_app.call(make_env(session_opt_in, "curl/8.4.0"))
body4.close if body4.respond_to?(:close)
unless status4 == 200
  warn "Expected HTTP 200 on dropped session request, got #{status4}"
  exit 1
end

if session_opt_in.key?("auth_token")
  warn "Expected session to be dropped when User-Agent changes under explicit session_hijacking"
  exit 1
end

puts "ok"

Origin Seeder

csx-seed