CVE-2011-1027
published 2011-03-20CVE-2011-1027: Off-by-one error in the convert_query_hexchar function in html.c in cgit.cgi in cgit before 0.8.3.5 allows remote attackers to cause a denial of service…
PriorityP421medium5CVSS 2.0
AVNACLAuNCNINAP
EPSS
3.75%
88.6th percentile
Off-by-one error in the convert_query_hexchar function in html.c in cgit.cgi in cgit before 0.8.3.5 allows remote attackers to cause a denial of service (infinite loop) via a string composed of a % (percent) character followed by invalid hex characters, as demonstrated by a %gg sequence.
Affected
26 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| lars_hjemli | cgit | <= 0.8.3.4 | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
| lars_hjemli | cgit | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
CWE
Excessive Iteration
mitre_cwe
CWE-834 Excessive Iteration
CWE-834: Excessive Iteration
The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.
If the iteration can be influenced by an attacker, this weakness could allow attackers to consume excessive resources such as CPU or memory. In many cases, a loop does not need to be infinite in order to cause enough resource consumption to adversely affect the product or its host system; it depends on the amount of resources consumed per iteration.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Availability. Impact: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification, DoS: Crash, Exit, or Restart. Excessive looping will cause unexpected consumption of resources, such as CPU cycl
CWE
Loop with Unreachable Exit Condition ('Infinite Loop')
mitre_cwe
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Availability. Impact: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification. An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typi
CWE
Insufficient Control Flow Management
mitre_cwe·CVSS 9.8
[CRITICAL] CWE-691 Insufficient Control Flow Management
CWE-691: Insufficient Control Flow Management
The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.
Modes of Introduction:
Phase: Architecture and Design
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Alter Execution Logic.
Examples:
The following function attempts to acquire a lock in order to perform operations on a shared resource.
However, the code does not check the value returned by pthread_mutex_lock() for errors. If pthread_mutex_lock() cannot acquire the mutex for any reason, the function may introduce a race condition into the program and result in undefined behavior.
In order to avoid data races, correctly written programs must check the result of thread syn
http://article.gmane.org/gmane.comp.version-control.git/168493http://hjemli.net/git/cgit/commit/?h=stable&id=fc384b16fb9787380746000d3cea2d53fccc548ehttp://lists.fedoraproject.org/pipermail/package-announce/2011-March/055896.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2011-March/055898.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2011-March/055966.htmlhttp://openwall.com/lists/oss-security/2011/03/07/3http://secunia.com/advisories/43633http://secunia.com/advisories/43788http://www.osvdb.org/71005http://www.securityfocus.com/bid/46756http://www.vupen.com/english/advisories/2011/0667https://bugzilla.redhat.com/show_bug.cgi?id=680905https://exchange.xforce.ibmcloud.com/vulnerabilities/65919http://article.gmane.org/gmane.comp.version-control.git/168493http://hjemli.net/git/cgit/commit/?h=stable&id=fc384b16fb9787380746000d3cea2d53fccc548ehttp://lists.fedoraproject.org/pipermail/package-announce/2011-March/055896.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2011-March/055898.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2011-March/055966.htmlhttp://openwall.com/lists/oss-security/2011/03/07/3http://secunia.com/advisories/43633http://secunia.com/advisories/43788http://www.osvdb.org/71005http://www.securityfocus.com/bid/46756http://www.vupen.com/english/advisories/2011/0667https://bugzilla.redhat.com/show_bug.cgi?id=680905https://exchange.xforce.ibmcloud.com/vulnerabilities/65919
2011-03-20
Published