UNKNOWN CVSS 4.0
Published: 2012-12-18

CVE-2012-5563

openstack folsom Security Advisory (CVE-2012-5563)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2012-5563?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2012-5563 impacting openstack folsom. Evaluated with CVSS Base Score of 4.0 (UNKNOWN).

Original NVD Description

Source: NIST NVD
OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by creating new tokens through token chaining. NOTE: this issue exists because of a CVE-2012-3426 regression.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Confidentiality
None (C:N)
No data confidentiality impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product openstack / folsom
Affected Versions 2012.2
Weakness Enumeration CWE-255

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2012-5563 impacting openstack folsom.

⚡ Nuclei Detection Template (YAML) cve-2012-5563.yaml
id: cve-2012-5563

info:
  name: openstack folsom - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: unknown
  description: |
    Automated signature & scanner for CVE-2012-5563 affecting openstack folsom.
    Evaluation: OpenStack Keystone, as used in OpenStack Folsom 2012.2, does not properly implement token expiration, which allows remote authenticated users to bypas...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2012-5563
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/Au:S/C:N/I:P/A:N
    cvss-score: 4.0
    cve-id: CVE-2012-5563
    cwe-id: CWE-255
  tags: cve,cve-2012-5563,openstack,folsom,unknown

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "folsom"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2012-5563.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2012-5563
# Target: openstack folsom | CVSS: 4.0 (UNKNOWN)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2012-5563 (openstack folsom)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against openstack folsom scope (2012.2).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2012-5563.sh
# Recommended Remediation & Patching Commands for CVE-2012-5563
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install folsom 2>/dev/null || \
sudo dnf upgrade folsom 2>/dev/null || \
sudo yum update folsom

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i folsom 2>/dev/null || rpm -qa | grep -i folsom

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2012-5563 in openstack folsom?

Review vendor-specific security notices and update openstack folsom packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2012-5563?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2012-5563?

CVE-2012-5563 is classified with a CVSS 3.1 Base Score of 4.0 (UNKNOWN). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
4.0
UNKNOWN SEVERITY
CVE ID CVE-2012-5563
Weakness CWE-255
Vendor openstack
Product folsom
Published 2012-12-18
Vector AV:N/AC:L/Au:S/C:N/I:P/A:N