Firewall Services ModuleHardware / appliance · Cisco
CVE-2013-1195
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 · uneditedThe time-based ACL implementation on Cisco Adaptive Security Appliances (ASA) devices, and in Cisco Firewall Services Module (FWSM), does not properly handle periodic statements for the time-range command, which allows remote attackers to bypass intended access restrictions by sending network traffic during denied time periods, aka Bug IDs CSCuf79091 and CSCug45850.
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 · high confidenceThe time-based ACL feature on Cisco ASA and FWSM devices uses the time-range command with periodic statements to define recurring access windows. Due to improper handling of these periodic statements in the time-range evaluation logic, the ACL fails to correctly deny traffic during configured blocked periods, allowing traffic to pass when it should be filtered.
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
Firewall Services ModuleHardware / appliance
all versions
Adaptive Security Appliance SoftwareOperating system
all versionsCVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 time-range configurationsRun 'show run time-range' or examine the device configuration for 'time-range' commands. Look for named time ranges defined in the configuration.Affected if Any time-range entries exist in the configuration
-
Check for periodic statementsWithin each time-range configuration, look for 'periodic' statements (e.g., 'periodic daily 00:00 to 23:59' or 'periodic weekdays 8:00 to 17:00'). Use 'show running-config time-range' to display full time-range definitions.Affected if Any time-range contains a 'periodic' keyword, as the vulnerability affects the evaluation logic for periodic statements
-
Verify time-range application to ACLsRun 'show run access-list' and search for any access-list entries that reference a time-range name. Check if time-based ACLs are applied to interfaces with 'access-group' commands.Affected if Time-range objects are referenced in active ACL entries applied to interfaces
-
Confirm device is an affected modelIdentify the device type and software version using 'show version'. Confirm it is a Cisco ASA or Firewall Services Module (FWSM) device.Affected if The device is a Cisco ASA or FWSM running any software version
If the device is a Cisco ASA or FWSM with any time-range configuration containing periodic statements that are applied to ACLs, the environment is affected by this vulnerability.
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 dataApply Cisco-provided patches for ASA and FWSM addressing Bug IDs CSCuf79091 and CSCug45850. Review existing time-based ACL configurations to identify any anomalies in enforcement, and consider additional compensating controls such as inline monitoring during the interim.
Fix this in Firewall Services Module
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,792.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1195 — 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-2013-1195 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