LiveActive security incident?Get immediate response
CVE Record

CVE-2011-1145: The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when...

The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2011-1145 is a possible buffer overflow in unixODBC before 2.2.14p2. It is triggered by an oversized SAVEFILE value in an ODBC connection string. Business risk depends on whether applications use old unixODBC versions and allow connection strings or SAVEFILE values to be influenced by users or external data.

Executive priority

Handle this as legacy dependency risk unless exposure analysis finds untrusted connection-string input. Prioritize remediation on systems running affected unixODBC versions in business-critical applications or environments where users can influence database connection parameters.

Technical view

The issue is in SQLDriverConnect() in unixODBC before 2.2.14p2. The source bundle describes a possible buffer overflow when a large SAVEFILE parameter is supplied in the connection string. No CVSS, CWE, confirmed impact, or exploit details are provided in the bundle.

Likely exposure

Exposure is most likely on legacy Linux or Unix systems running unixODBC before 2.2.14p2, especially where applications dynamically build ODBC connection strings. Exposure is lower where connection strings are static, access-controlled, and not influenced by untrusted input.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. It only supports that a large SAVEFILE connection-string value may trigger a buffer overflow condition. Practical exploitability and impact are not established by the supplied sources.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed impact is present in the supplied bundle. The version boundary before 2.2.14p2 is clear, but validation should focus on real package versions and whether the vulnerable code path is reachable.

Mitigation direction

  • Inventory systems and applications using unixODBC.
  • Upgrade unixODBC to 2.2.14p2 or a vendor-fixed package.
  • Check Debian, Red Hat, and SUSE guidance for package-specific status.
  • Restrict who can modify ODBC connection strings or SAVEFILE values.
  • Treat externally supplied connection-string data as unsafe input.

Validation and detection

  • Confirm installed unixODBC package versions across managed hosts.
  • Identify applications that call SQLDriverConnect() through unixODBC.
  • Review whether SAVEFILE or connection strings accept untrusted input.
  • Verify vendor advisory status for each distribution package.
  • Regression test ODBC connection workflows after updating packages.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2011-1145 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
unixodbcunixodbcbefore 2.2.14p2Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.