Enterprise Linux Openstack PlatformOperating system · Redhat
CVE-2015-5694
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 · uneditedDesignate does not enforce the DNS protocol limit concerning record set sizes
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 confidenceDesignate (OpenStack DNS service) fails to enforce DNS protocol RFC limits on record set sizes during record creation or updates. This allows users to create oversized DNS record sets that can cause protocol violations, potentially leading to malformed DNS responses or denial of service when downstream resolvers cannot handle the oversized records.
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
Enterprise Linux Openstack PlatformOperating system
= 7
Debian LinuxOperating system
= 8.0= 9.0= 10.0= 1.0.0= 1.0.0.0= 2015.1.0CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Confirm Designate is installedRun 'rpm -qa | grep designate' on RHEL or 'dpkg -l | grep designate' on Debian to list installed Designate packagesAffected if No Designate package is found, the system is not affected by this CVE
-
Identify installed Designate versionRun 'rpm -qi openstack-designate-common' on RHEL or 'dpkg -s designate-common' on Debian to get the exact version numberAffected if The installed version matches 1.0.0, 1.0.0.0, or 2015.1.0 exactly, indicating a vulnerable version
-
Verify Designate API service is runningRun 'systemctl status openstack-designate-api' or check if the Designate API process is listening on port 9001 (default API port)Affected if The service is not running, the vulnerability cannot be exploited at this time
-
Test ability to create oversized DNS recordsUse Designate API or CLI (openstack recordset create) to attempt creating a DNS record with an unusually large value (e.g., TXT record with several KB of data)Affected if The API accepts the oversized record without rejecting it based on DNS protocol RFC limits, the system is vulnerable
-
Inspect existing DNS records for oversized entriesQuery Designate database or use 'openstack recordset list' to review existing record set sizesAffected if Record sets exist that exceed typical DNS limits (e.g., TXT records over 255 bytes without proper splitting), the vulnerability is present
A system is affected if it runs Designate version 1.0.0, 1.0.0.0, or 2015.1.0 and allows DNS records exceeding RFC 1035 size limits to be created or already contains such oversized records.
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 dataImplement validation checks in Designate to enforce DNS protocol limits on record set sizes (per RFC 1035 and related RFCs) and reject records that exceed these limits during creation or modification.
Fix this in Enterprise Linux Openstack Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5694 — 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-2015-5694 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