usn-2380-1
Vulnerability from osv_ubuntu
Published
2014-10-09 12:48
Modified
2026-02-10 04:40
Summary
bash vulnerabilities
Details

Michal Zalewski discovered that Bash incorrectly handled parsing certain function definitions. If an attacker were able to create an environment variable containing a function definition with a very specific name, these issues could possibly be used to bypass certain environment restrictions and execute arbitrary code. (CVE-2014-6277, CVE-2014-6278)

Please note that the previous Bash security update, USN-2364-1, includes a hardening measure that prevents these issues from being used in a Shellshock attack.

References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "cves_map": {
          "cves": [
            {
              "id": "CVE-2014-6277",
              "severity": [
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            },
            {
              "id": "CVE-2014-6278",
              "severity": [
                {
                  "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
                  "type": "CVSS_V3"
                },
                {
                  "score": "medium",
                  "type": "Ubuntu"
                }
              ]
            }
          ],
          "ecosystem": "Ubuntu:14.04:LTS"
        }
      },
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "bash",
            "binary_version": "4.3-7ubuntu1.5"
          },
          {
            "binary_name": "bash-builtins",
            "binary_version": "4.3-7ubuntu1.5"
          },
          {
            "binary_name": "bash-static",
            "binary_version": "4.3-7ubuntu1.5"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:14.04:LTS",
        "name": "bash",
        "purl": "pkg:deb/ubuntu/bash@4.3-7ubuntu1.5?arch=source\u0026distro=trusty"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.3-7ubuntu1.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.2-5ubuntu3",
        "4.3-1ubuntu2",
        "4.3-2ubuntu1",
        "4.3-3ubuntu1",
        "4.3-4ubuntu1",
        "4.3-4ubuntu2",
        "4.3-6ubuntu1",
        "4.3-7ubuntu1",
        "4.3-7ubuntu1.1",
        "4.3-7ubuntu1.2",
        "4.3-7ubuntu1.3",
        "4.3-7ubuntu1.4"
      ]
    }
  ],
  "aliases": [],
  "details": "Michal Zalewski discovered that Bash incorrectly handled parsing certain\nfunction definitions. If an attacker were able to create an environment\nvariable containing a function definition with a very specific name, these\nissues could possibly be used to bypass certain environment restrictions\nand execute arbitrary code. (CVE-2014-6277, CVE-2014-6278)\n\nPlease note that the previous Bash security update, USN-2364-1, includes\na hardening measure that prevents these issues from being used in a\nShellshock attack.\n",
  "id": "USN-2380-1",
  "modified": "2026-02-10T04:40:50Z",
  "published": "2014-10-09T12:48:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-2380-1"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2014-6277"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2014-6278"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "summary": "bash vulnerabilities",
  "upstream": [
    "UBUNTU-CVE-2014-6277",
    "UBUNTU-CVE-2014-6278"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.