Network Satellite ServerApplication · Redhat
CVE-2011-0717
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSession fixation vulnerability in Red Hat Network (RHN) Satellite Server 5.4 allows remote attackers to hijack web sessions via unspecified vectors related to Spacewalk.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSession fixation vulnerability in RHN Satellite Server 5.4 and Spacewalk allows remote attackers to manipulate or set the session ID that a victim user will use, enabling hijacking of authenticated web sessions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Network Satellite ServerApplication
= 5.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if RHN Satellite Server or Spacewalk is installedCheck for the product by looking for its installation directories or running 'rpm -qa | grep -i satellite' or 'rpm -qa | grep -i spacewalk'Affected if RHN Satellite Server version 5.4 or Spacewalk is found on the system
-
Determine the installed versionRun 'rpm -q rhn-satellite' or check the version through the web interface login page or /var/log/rhn/rhn_satellite_access.logAffected if The version is exactly 5.4 for RHN Satellite Server, or an unpatched version of Spacewalk that predates the fix
-
Verify web interface exposureCheck if the web UI is accessible by attempting to reach the Satellite server URL on ports 443 or 80Affected if The web interface is exposed and accessible remotely or from untrusted networks
-
Inspect session configurationExamine the session handling configuration files in the Apache conf directory (typically /etc/httpd/conf.d/) or the application configuration for session ID regeneration settingsAffected if Session IDs are not being regenerated upon user authentication (session fixation is possible)
-
Check for recent authentication logsReview /var/log/rhn/rhn_satellite_access.log and /var/log/rhn/rhn_web_ui.log for suspicious session activity or unusual session ID patternsAffected if Multiple requests using the same session ID are observed from different source IPs, indicating session fixation
A system is affected if it runs RHN Satellite Server 5.4 or an unpatched Spacewalk instance with an exposed web interface where session IDs are not regenerated upon authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of RHN Satellite Server or Spacewalk that addresses session fixation. Enforce new session ID generation upon authentication and implement proper session invalidation.
Fix this in Network Satellite Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-0717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data