{"api_version":"1","generated_at":"2026-05-12T21:48:09+00:00","cve":"CVE-2021-21277","urls":{"html":"https://cve.report/CVE-2021-21277","api":"https://cve.report/api/cve/CVE-2021-21277.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2021-21277","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2021-21277"},"summary":{"title":"CVE-2021-21277","description":"angular-expressions is \"angular's nicest part extracted as a standalone module for the browser and node\". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call \"expressions.compile(userControlledInput)\" where \"userControlledInput\" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a \".constructor.constructor\" technique. In terms of impact: If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2021-02-01 15:15:00","updated_at":"2022-10-19 19:06:00"},"problem_types":["CWE-94"],"metrics":[],"references":[{"url":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq","name":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq","refsource":"CONFIRM","tags":["Vendor Advisory"],"title":"Angular Expressions - Remote Code Execution · Advisory · peerigon/angular-expressions · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://www.npmjs.com/package/angular-expressions","name":"https://www.npmjs.com/package/angular-expressions","refsource":"MISC","tags":["Product"],"title":"angular-expressions","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html","name":"http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html","refsource":"MISC","tags":["Vendor Advisory"],"title":"AngularJS: Angular 1.6 - Expression Sandbox Removal","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1","name":"https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1","refsource":"MISC","tags":["Patch","Third Party Advisory"],"title":"Fix Security Vulnerability by using hasOwnProperty defensively · peerigon/angular-expressions@07edb62 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-21277","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21277","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2021","cve_id":"21277","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"peerigon","cpe5":"angular-expressions","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"node.js","cpe12":"*","cpe13":"*"},{"cve_year":"2021","cve_id":"21277","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"peerigon","cpe5":"angular-expressions","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"node.js","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2021-21277","qid":"982961","title":"Nodejs (npm) Security Update for angular-expressions (GHSA-j6px-jwvv-vpwq)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2021-21277","STATE":"PUBLIC","TITLE":"Angular Expressions - Remote Code Execution"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"angular-expressions","version":{"version_data":[{"version_value":"< 1.1.2"}]}}]},"vendor_name":"peerigon"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"angular-expressions is \"angular's nicest part extracted as a standalone module for the browser and node\". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call \"expressions.compile(userControlledInput)\" where \"userControlledInput\" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a \".constructor.constructor\" technique. In terms of impact: If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":8.5,"baseSeverity":"HIGH","confidentialityImpact":"LOW","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"CHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')"}]}]},"references":{"reference_data":[{"name":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq","refsource":"CONFIRM","url":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq"},{"name":"https://www.npmjs.com/package/angular-expressions","refsource":"MISC","url":"https://www.npmjs.com/package/angular-expressions"},{"name":"http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html","refsource":"MISC","url":"http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html"},{"name":"https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1","refsource":"MISC","url":"https://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1"}]},"source":{"advisory":"GHSA-j6px-jwvv-vpwq","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2021-02-01 15:15:00","lastModifiedDate":"2022-10-19 19:06:00","problem_types":["CWE-94"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":8.8,"baseSeverity":"HIGH"},"exploitabilityScore":2.8,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:S/C:P/I:P/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"SINGLE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":6.5},"severity":"MEDIUM","exploitabilityScore":8,"impactScore":6.4,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:peerigon:angular-expressions:*:*:*:*:*:node.js:*:*","versionEndExcluding":"1.1.2","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2021","CveId":"21277","Ordinal":"195403","Title":"CVE-2021-21277","CVE":"CVE-2021-21277","Year":"2021"},"notes":[{"CveYear":"2021","CveId":"21277","Ordinal":"1","NoteData":"angular-expressions is \"angular's nicest part extracted as a standalone module for the browser and node\". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call \"expressions.compile(userControlledInput)\" where \"userControlledInput\" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a \".constructor.constructor\" technique. In terms of impact: If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.","Type":"Description","Title":null},{"CveYear":"2021","CveId":"21277","Ordinal":"2","NoteData":"2021-02-01","Type":"Other","Title":"Published"},{"CveYear":"2021","CveId":"21277","Ordinal":"3","NoteData":"2021-02-01","Type":"Other","Title":"Modified"}]}}}